Currently, polyline markups retrieved via the MCP list_markups_in_pdf tool only return a bounding box (x, y, width, height) — not the actual vertex geometry of the line. For conduit runs and other polyline markups, the bounding box is nearly useless for spatial analysis because it tells you nothing about where the line actually starts, ends, or bends.
The partial solution that exists but doesn't scale:The get_markup_shape tool can retrieve vertex data for individual markups, and it works well — but it only operates one markup at a time. On drawings with hundreds or thousands of conduit polylines, making a separate API call per markup is completely impractical. The round-trip overhead makes bulk AI-assisted automation prohibitively slow.
What we're asking for:Allow vertex geometry to be included as an opt-in returnable property in list_markups_in_pdf, following the same pattern already used for custom columns. For polyline and polygon markup types, this would return:
- Vertices — the ordered list of x,y coordinate pairs along the path
- Start point and end point as discrete fields
- Midpoint (or midpoint index) for label placement purposes
- Coordinate space consistent with the existing bounding box values
Why it matters:In MEP coordination workflows for large data center projects, AI tools working through the MCP API need to determine which equipment a conduit connects to based on where its endpoints land spatially. Right now that requires exporting the PDF and parsing raw annotation data with a third-party library (PyMuPDF) — cross-referencing annotation IDs manually to get vertex arrays. That workaround is fragile, slow, and breaks the otherwise clean MCP-native workflow.
If vertex data were batch-returnable alongside comment, subject, and custom columns in a single list_markups_in_pdf call, it would unlock fully automated From/To population, conduit schedule generation, and spatial connection mapping — all without leaving the Bluebeam MCP environment.
This would be a high-value addition for any team doing MEP, conduit, or structural coordination automation in Revu.
