Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Checklist Item Attachment

create_checklist_item_attachment

Upload an attachment to a checklist item in Procore inspections. Provide list, item, project, and section IDs along with the file.

Instructions

Uploads an Attachment to the specified Checklist Item. Use this to create a new Inspections in Procore. Creates a new Inspections and returns the created object on success (HTTP 201). Required parameters: list_id, item_id, project_id, section_id, attachment. Procore API: Project Management > Inspections. Endpoint: POST /rest/v1.0/checklist/lists/{list_id}/items/{item_id}/item_attachments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesURL path parameter — unique identifier of the list
item_idYesURL path parameter — unique identifier of the item
project_idYesJSON request body field — the ID of the Project the Item belongs to
section_idYesJSON request body field — the ID of the Section the Item belongs to
attachmentYesJSON request body field — item Attachment. To upload an attachment you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with the `attachment` file.
Behavior3/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds that it returns HTTP 201 and the created object, which is consistent. No contradictions, but little additional behavior is disclosed beyond what annotations and schema imply.

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?

The description is short but contains irrelevant and incorrect repetition about creating inspections. It could be more concise by removing the erroneous statements. The essential upload purpose is stated, but wasted space lowers efficiency.

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?

Given no output schema and a confusing description, the tool's purpose is muddled. It does not explain what happens to the attachment after upload, nor does it clarify the relationship to inspections. The misleading 'create inspections' text further reduces completeness.

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 redundantly lists required parameters but adds no new meaning beyond what the schema already provides. The multipart/form-data note is in the schema, not the description.

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

Purpose2/5

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

The description begins by stating 'Uploads an Attachment to the specified Checklist Item,' which is clear. However, it then incorrectly states 'Use this to create a new Inspections in Procore' and repeats 'Creates a new Inspections,' which is contradictory and misleading. The tool is for attaching to an existing item, not creating inspections.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Sibling tools like bulk_create_checklist_inspections_item_attachments exist, but no differentiation is provided. The description simply lists required parameters without context.

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