Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Budget Details

list_budget_details

Retrieve all rows from the Budget Detail Report for a specific project and budget view. Apply filters by cost code, vendor, or cost type to refine results.

Instructions

Return a list of all rows from the Budget Detail Report for a Project and Budget View. Note: In addition to all the fields outlined in the response example, there will be an additional key for each visible, non-formula, non-qualitative column (Ex: Original Budget Amount, Budget Modifications, Forecast to Complete, and Source Columns). The integer keys returned represent the IDs of the budget columns which are returned by the Budget Detail Columns API. As well, valid filter values can be fo... Use this to perform the list budget action on Budget records. Creates a new Budget records and returns the created object on success (HTTP 201). Required parameters: budget_view_id, project_id. Procore API: Construction Financials > Budget. Endpoint: POST /rest/v1.0/budget_views/{budget_view_id}/budget_details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_view_idYesURL path parameter — unique identifier of the budget view
project_idYesQuery string parameter — unique identifier for the project.
billerNoJSON request body field — sub Job Filter, can pass Sub Job or Project
cost_codeNoJSON request body field — cost Code Filter
root_cost_codeNoJSON request body field — division Filter
cost_typeNoJSON request body field — cost Type Filter
vendorNoJSON request body field — vendor Filter
detail_typeNoJSON request body field — detail Type Filter
Behavior2/5

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

Annotations indicate not read-only, not destructive, not idempotent, which aligns with a potential mutation. However, the description mixes list and create behaviors without clarifying whether the tool solely retrieves data or also creates records. The note about response fields adds some transparency, but the overall behavior is ambiguous.

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

Conciseness2/5

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

The description is poorly structured—contains contradictory statements (list vs. create), truncation, and irrelevant details like the API endpoint and HTTP status. Sentences do not build a coherent narrative, making it verbose and confusing.

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

Completeness1/5

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

Without an output schema, the description should explain return structure, pagination, and error handling, but it only vaguely mentions extra response fields. The contradictory create action is misleading. Given the tool's complexity and many sibling tools, the description fails to provide adequate context for correct invocation.

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% coverage with descriptions for all 8 parameters. The description only adds that budget_view_id and project_id are required, which is already in the schema. The incomplete mention of filter values does not meaningfully enhance parameter understanding.

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 states 'Return a list of all rows from the Budget Detail Report', which suggests a read operation, but immediately contradicts with 'Creates a new Budget records', making the actual purpose unclear. The title and name suggest listing, but the description includes creation logic, confusing the tool's core function.

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 does not specify when to use this tool over alternatives like list_budget_views or list_budget_modifications. It mentions filters but truncates ('valid filter values can be fo...'), providing no context for appropriate usage scenarios or exclusions.

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