Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Budget View Snapshot.

create_a_budget_view_snapshot

Create a project-level budget view snapshot for project status or ad hoc type. Specify the project, budget view, and name to generate a new snapshot record in Procore.

Instructions

Create a project-level snapshot for either project status or ad hoc type. This is rate limited to one request per hour for each project and budget view, regardless of snapshot type. Use this to create a new Budget records in Procore. Creates a new Budget records and returns the created object on success (HTTP 201). Required parameters: project_id, budget_template_id, name. Procore API: Construction Financials > Budget. Endpoint: POST /rest/v1.0/budget_view_snapshots

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesJSON request body field — the project identifier
budget_template_idYesJSON request body field — the budget template identifier (deprecated, use budget_view_id instead)
budget_view_idNoJSON request body field — the budget view identifier (replaces budget_template_id)
nameYesJSON request body field — title of the budget view snapshot
descriptionNoJSON request body field — description of the budget snapshot
snapshot_typeNoJSON request body field — snapshot Type. Only available when Project Status Snapshots feature is enabled.
approval_statusNoJSON request body field — approval Status.
status_idNoJSON request body field — the ID of a custom status. Only available when the Custom Statuses feature is enabled. When enabled, use this parameter instead of approval_status. The status_id must reference an available custom ...
Behavior3/5

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

Description discloses rate limiting and HTTP 201 return status, which are beyond annotations. Annotations provide no behavioral details (readOnlyHint=false is consistent). No contradictions. However, it lacks deeper behavioral context like what happens on failure.

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?

Description is short and front-loads purpose, but contains unnecessary repetition ('Creates a new Budget records' twice) and a misleading phrase. Some sentences could be merged.

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, the description only states it returns the created object. It does not explain error handling, the deprecation of budget_template_id, or edge cases like the 'Custom Statuses' feature. Provides API endpoint and rate limit.

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 the description's mention of required parameters is redundant. It adds no additional semantics for enum fields (snapshot_type, approval_status) or the budget_view_id vs budget_template_id deprecation.

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 the action ('Create a project-level snapshot') and resource ('budget view snapshot'), but then contradicts itself by saying 'Creates a new Budget records', which conflates two different concepts and could mislead the AI agent. The API endpoint confirms it's about budget view snapshots.

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?

The description provides a rate limit constraint (one request per hour) which helps in usage, but it does not differentiate this tool from siblings like 'create_budget_line_item' or 'list_budget_view_snapshots'. No explicit guidance on when to use or not use this tool.

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