Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Drawings

list_drawings
Read-onlyIdempotent

Lists all drawings in a drawing area with pagination and filtering. Retrieve drawing IDs and details for a specific project area.

Instructions

Returns a list of all Drawings for a specified drawing area. 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: drawing_area_id. Procore API (v1.1): Project Management > Drawings. Endpoint: GET /rest/v1.1/drawing_areas/{drawing_area_id}/drawings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drawing_area_idYesURL path parameter — iD of the drawing area
project_idNoQuery string 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)
filters__drawing_discipline_idNoQuery string parameter — returns a list of drawings that are linked to the provided drawing_discipline_id
filters__drawing_set_idNoQuery string parameter — returns a list of drawings that are linked to the provided drawing_set_id. Can optionally pass 'current_set' to return only drawings that are published.
with_positionNoQuery string parameter — returns a list of drawings conditionally ordered by position. By default, it will order by position.
viewNoQuery string parameter — the 'compact' view returns the minimal attributes of a drawing (id, number, title, obsolete, and discipline). The 'extended' view returns minimal attributes with the current_revision object, which ...
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent. The description adds behavioral details: paginated JSON array response, pagination metadata, and the Procore API endpoint. No contradictions 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 concise: two sentences covering purpose, usage, and behavior, plus optional API reference. Every sentence adds value with no redundancy.

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?

For an 8-parameter tool with no output schema, the description covers the main points: what it returns, pagination, required parameter, and API context. It does not explain all filter parameters, but the schema covers those. Adequate for agent decision-making.

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?

Schema description coverage is 100%, so baseline is 3. The description highlights drawing_area_id as required and page/per_page for pagination, but does not add significant semantic meaning beyond what the schema already provides for each parameter.

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 states it returns a list of all Drawings for a specified drawing area, with specific use cases like paginated overview, finding IDs, and filtering. It distinguishes this tool from siblings (e.g., list_drawing_areas) by focusing on drawings and the required drawing_area_id.

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 provides explicit use cases: enumeration, paginated overview, ID lookup, and filtering. It mentions the required parameter and pagination controls. However, it does not explicitly state when not to use this tool or mention alternative tools for related resources.

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