Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Drawing Revisions

list_drawing_revisions
Read-onlyIdempotent

Retrieve a paginated list of drawing revisions for a project. Filter by drawing ID, area, discipline, set, or revision status to find specific revisions.

Instructions

Returns a list of all Drawing Revisions in the specified Project. Use this to enumerate Drawings when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Drawings. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Drawings. Endpoint: GET /rest/v1.0/projects/{project_id}/drawing_revisions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
drawing_area_idNoQuery string parameter — filter by Drawing Area
drawing_idNoQuery string parameter — unique identifier of the drawing
drawing_discipline_idNoQuery string parameter — filter by Drawing Discipline
drawing_set_idNoQuery string parameter — filter by Drawing Set. To retreive revisions from current set add `drawing_set_id=current_set` to query
idNoQuery string parameter — filter by Drawing Revision ID To request specific drawing revision ids add `id[]=42&id[]=43` to query
filters__idsNoQuery string parameter — filter by Drawing Revisions ID To request specific drawing revision ids add `filters[ids]=[1,2,3]` to filters
filters__updated_atNoQuery string parameter — return item(s) updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-...
filters__deletedNoQuery string parameter — include deleted drawing revisions. Deleted drawing revisions are filtered by default.
is_reviewedNoQuery string parameter — filter by `reviewed` status
queryNoQuery string parameter — filter by custom query
with_obsoleteNoQuery string parameter — include obsolete drawing revisions. Obsolete drawing revisions are filtered by default.
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
viewNoQuery string parameter — defines the type of view returned. Must be one of 'only_pdf_urls', 'only_ids', 'only_ids_post_review', 'web_index', 'web_show', 'extended_coordinates', 'extended_files', 'extended_dpi' or 'android'.
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds that it returns a paginated JSON array with metadata, which is helpful but not extensive. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise, with only 4-5 sentences that front-load purpose, usage, return type, pagination, required parameter, and API endpoint. Every sentence adds value; no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 16 parameters, the schema covers all details. The description explains pagination and mentions 'paginated JSON array of Drawings' with metadata, which is sufficient for a list tool. Could be slightly more explicit about the response structure but overall complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the description does not need to detail each parameter. It mentions pagination parameters (page, per_page) but does not add meaning beyond the schema. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the resource as 'Drawing Revisions' within a project, uses the verb 'Returns a list' and provides context for use (enumerate, find IDs, filter). It distinguishes from sibling tools like 'list_drawings' by naming revisions explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool ('when you need a paginated overview, to find IDs, or to filter by query parameters') and covers pagination controls, but does not mention when not to use it or provide explicit alternatives among the many sibling list tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TylerIlunga/procore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server