Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Dumpster Logs

list_dumpster_logs
Read-onlyIdempotent

Retrieve Dumpster Logs for a project with optional date filters and pagination. Returns a paginated JSON array of daily dumpster log records.

Instructions

Returns all Dumpster Logs for the current date. See Working with Daily Logs for information on filtering the response using the log_date, start_date, and end_date parameters. Note that if none of the date parameters are provided in the call, only logs from the current date are returned. Use this to enumerate Daily Log records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Daily Log records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Daily Log. Endpoint: GET /rest/v1.0/projects/{project_id}/dumpster_logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
log_dateNoQuery string parameter — date of specific logs desired in YYYY-MM-DD format
start_dateNoQuery string parameter — start date of specific logs desired in YYYY-MM-DD format (use together with end_date)
end_dateNoQuery string parameter — end date of specific logs desired in YYYY-MM-DD format (use together with start_date)
filters__created_by_idNoQuery string parameter — returns item(s) created by the specified User IDs.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor IDs.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__daily_log_segment_idNoQuery string parameter — daily Log Segment ID filter
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by explaining default behavior (current date if no date params), pagination details, and mention of pagination metadata. No contradictions.

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 moderately long but well-structured: main feature, link, note, guidance, return type, pagination, required params, and API endpoint. It could be streamlined but is not overly verbose.

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?

For a list operation with comprehensive schema annotations, the description covers key behaviors (date defaults, pagination), required parameters, and output type. It is sufficient 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?

Schema coverage is 100% with good parameter descriptions. The description adds some extra context (e.g., date parameters default to current date, log_date vs start/end usage) but does not significantly enhance understanding 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 the tool returns all Dumpster Logs for the current date, with options to filter by date range. However, it does not explicitly differentiate from sibling tools like other daily log listers (e.g., list_call_logs, list_manpower_logs).

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 says when to use: for paginated overview, finding IDs, or filtering. It also includes a link to documentation for filtering. It lacks explicit when-not-to-use or alternatives, but the provided context is helpful.

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