Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Submittal Associated Attachments

list_submittal_associated_attachments
Read-onlyIdempotent

Retrieve a paginated list of submittal attachments for a project. Use this tool to find attachment IDs or filter by query parameters. Requires project_id.

Instructions

List Submittal Associated Attachments for the specified Project. Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Submittals. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Submittals. Endpoint: GET /rest/v1.0/submittal_associated_attachments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
viewNoQuery string parameter — view for which you are exporting
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already declare safe read-only behavior. The description adds pagination details (page, per_page, pagination metadata) useful for correct invocation.

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

Conciseness3/5

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

Four sentences with some redundancy. The inconsistency wastes useful space, but the structure is acceptable.

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

Completeness2/5

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

No output schema. Description mentions paginated JSON but due to inconsistency (submittals vs attachments), it's unclear what is returned. Lacks details on response fields.

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?

Input schema has 100% description coverage. The description mentions page and per_page but does not add significant meaning beyond what the schema provides.

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

Purpose3/5

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

The description states it lists submittal associated attachments but then refers to enumerating submittals, creating inconsistency. The verb and resource are clear enough, but the ambiguity reduces clarity.

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

Usage Guidelines1/5

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

The description explicitly says 'enumerate Submittals' which is misleading—the tool lists attachments, not submittals. It provides no guidance on when to use this vs list_submittals or list_submittal_attachments.

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