Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Budget View Snapshot Detail Rows

list_budget_view_snapshot_detail_rows
Read-onlyIdempotent

Retrieve paginated budget view snapshot detail rows for project status and ad hoc types. Filter by biller, cost code, category, or budget line item.

Instructions

Returns a list of all budget view snapshots detail rows for project status and ad hoc types. Note: In addition to all the fields outlined in the response, there will be an additional key for each visible source and formula column created for the particular budget view. As well, when using a Forecasting View ID, additional keys will be visible that give calculated forecasts for each month, as defined by the Advanced Forecasting Tool. 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}/detail_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
sortNoQuery string parameter — return item(s) with the specified sort. Default is biller_type,biller,root_cost_code,cost_code,category_id
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 id field will be null for rows that have...
Behavior4/5

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

Annotations declare readOnlyHint, destructiveHint, and idempotentHint. The description adds behavioral details: paginated results, JSON array with pagination metadata, additional keys for source/formula columns, and forecasting view keys. This adds value beyond annotations without contradiction.

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 a single paragraph, somewhat verbose with repeated mentions of pagination and API endpoint info. It front-loads the main function but includes redundant phrases. Could be more concise.

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

Completeness3/5

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

No output schema exists, so the description partially explains the response (JSON array, pagination metadata, extra keys). It mentions required parameters and API details. However, it lacks clarification on what 'project status and ad hoc types' means and does not differentiate from sibling tools. Somewhat complete but with gaps.

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 coverage is 100%, so baseline is 3. The description highlights required parameters (budget_view_snapshot_id, project_id) and pagination controls (page, per_page), but does not detail other parameters. The schema itself provides descriptions, so the description adds limited extra meaning.

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 it returns a list of budget view snapshot detail rows with specific verb and resource. It also mentions usage for paginated overview and filtering. However, it does not explicitly distinguish from sibling tools like list_budget_view_detail_rows or list_budget_view_snapshot_summary_rows, which share similar names and purposes.

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

Usage Guidelines3/5

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

The description advises using this tool for enumerating budget records, paginated overview, finding IDs, and filtering. It mentions required parameters but lacks explicit guidance on when not to use it or alternatives. Given sibling tools exist, this is a gap.

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