Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Delivery Logs

list_delivery_logs
Read-onlyIdempotent

List delivery logs for a project with filters for date, status, creator, and segment. Returns paginated results.

Instructions

Returns all approved Delivery 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}/delivery_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__statusNoQuery string parameter — filter on status for "pending" or "approved" or "all"
filters__created_by_idNoQuery string parameter — returns item(s) created by the specified User 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?

Description adds behavioral context beyond annotations: only returns approved logs, uses current date if no params, paginated, with link to docs. No contradiction with annotations.

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

Conciseness5/5

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

Description is concise, front-loaded with purpose, includes link and endpoint info. Every sentence adds value.

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

Completeness5/5

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

For a list tool with no output schema, description adequately specifies return type ('paginated JSON array') and pagination controls, making it complete for an agent.

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 detailed parameter descriptions. Description reiterates date filtering and pagination but adds little new semantic value. Baseline 3 appropriate.

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

Purpose5/5

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

Description clearly states it returns all approved Delivery Logs for the current date, with a specific verb ('returns') and resource ('Delivery Logs'). Also mentions filtering capabilities.

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?

Provides usage context: enumerate daily log records for paginated overview, find IDs, filter by query parameters. Mentions default date behavior. Lacks explicit when-not-to-use or alternatives.

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