Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Budget View Snapshot Summary Rows

list_budget_view_snapshot_summary_rows
Read-onlyIdempotent

Retrieve paginated summary rows from budget view snapshots to enumerate budget records, find IDs, and filter by biller, cost code, or category. Use for project budget overview.

Instructions

Returns a list of all budget view snapshots summary rows for project status and ad hoc types. The type of row returned is dependent on the value used in the group_by query param. Note: In addition to all the fields outlined in the response, there will be an additional key for each visible standard, source, and formula column created for the particular budget view. Use this to enumerate Budget records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Budget records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: budget_view_snapshot_id, project_id. Procore API: Construction Financials > Budget. Endpoint: GET /rest/v1.0/budget_view_snapshots/{budget_view_snapshot_id}/summary_rows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_view_snapshot_idYesURL path parameter — budget View Snapshot ID
project_idYesQuery string parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
biller__NoQuery string parameter — return item(s) within a specific biller. Format is biller[]=id=1,type=SubJob or biller[]=id=1,type=Project
cost_code_id__NoQuery string parameter — return item(s) within a specific Cost Code id or range of Cost Code IDs
cost_code_name__NoQuery string parameter — return item(s) within a specific Cost Code name or range of Cost Code names
root_cost_code_id__NoQuery string parameter — return item(s) within a specific Root Cost Code id or range of Root Cost Code IDs
root_cost_code_name__NoQuery string parameter — return item(s) within a specific Root Cost Code name or range of Root Cost Code names
category_id__NoQuery string parameter — return item(s) within a specific category id (line item type id) or range of category IDs
budget_line_item_id__NoQuery string parameter — return item(s) within a specific budget line item id or range of budget line item IDs
group_byNoQuery string parameter — groups the data. Value can be a comma separated string. Default is biller,root_cost_code
budget_row_typeNoQuery string parameter — return budgeted, unbudgeted or all item(s) from all budget rows for a project. Default is all. Note that when the unbudgeted or all values are supplied, the subtotals may change depending on the pr...
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's mention of a read operation is consistent. The description adds value by disclosing pagination behavior, response metadata, and the presence of additional dynamic columns, which go beyond the annotations.

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?

The description is well-structured, starting with purpose, then usage guidance, followed by behavioral notes and API reference. While it is somewhat lengthy, every sentence adds relevant information without redundancy.

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

Completeness4/5

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

Given the tool's 13 parameters and no output schema, the description adequately covers the purpose, usage context, pagination, and operational behavior (e.g., additional columns). The API source is also mentioned. It is sufficiently complete for an agent to understand and invoke the tool correctly.

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?

With 100% schema coverage, the description does not need to explain parameters in depth. It mentions that group_by affects row type and that page/per_page control pagination, but this does not add significant meaning beyond the schema.

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

Purpose4/5

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

The description clearly states that it returns a list of budget view snapshot summary rows, referencing the dependency on the group_by parameter. It adequately distinguishes from sibling tools like list_budget_view_snapshot_detail_rows by emphasizing 'summary rows' and 'paginated overview', though no explicit comparison is made.

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

Usage Guidelines4/5

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

The description provides specific use cases: to enumerate budget records, find IDs, or filter by query parameters. It gives context for when to use the tool but does not mention when to use alternatives like detail rows.

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