Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Action Plan Template Reference

create_project_action_plan_template_reference

Create a new action plan template reference in Procore by providing project ID, template item ID, reference type, and payload. This tool adds a reference to an action plan template item.

Instructions

Create Project Action Plan Template Reference. Use this to create a new Action Plans in Procore. Creates a new Action Plans and returns the created object on success (HTTP 201). Required parameters: project_id, plan_template_item_id, type, payload. Procore API: Project Management > Action Plans. Endpoint: POST /rest/v1.0/projects/{project_id}/action_plans/plan_template_references

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
plan_template_item_idYesJSON request body field — project Action Plan Template Item ID
typeYesJSON request body field — action Plan Reference Type
payloadYesJSON request body field — one of attachment, drawing_revision_id, file_version_id, specification_section_id, generic_tool_item_id, form_id, image_id, meeting_id, or observation_item_id is accepted depending on the type prov...
Behavior2/5

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

Annotations provide readOnlyHint=false and openWorldHint=true, but the description adds little: it mentions HTTP 201 success but no disclosure of side effects, permission requirements, or error conditions. The openWorldHint suggests unknown side effects, which the description does not address.

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

Conciseness4/5

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

Three sentences covering purpose, usage direction, and endpoint info. Efficient but could be more structured. The first sentence is somewhat redundant with the title.

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?

Missing crucial details: what a 'plan template reference' is, how it differs from regular references, and the structure of the returned object. The description does not leverage the fact that there is no output schema to explain response fields. The mismatch between 'Action Plans' in description and 'plan_template_references' in endpoint 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 coverage is 100% so all parameters are documented. The description lists the required parameters but adds no additional meaning beyond the schema. It does not explain the relationship between 'type' and 'payload' or provide examples.

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 creates a new 'Action Plans' but the tool name and endpoint suggest it creates a template reference. The mention of 'plan_template_references' in the last line clarifies, but the first sentence is potentially misleading. It communicates a create operation but the resource is ambiguous.

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 explicit guidance on when to use this tool versus alternatives like create_action_plan_reference or bulk_create_plan_template_references. The description lists required parameters and endpoint but does not provide context for selection.

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