Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Inspection Logs

list_inspection_logs
Read-onlyIdempotent

Fetch paginated inspection logs for a project. Filter by date range, creator ID, or location ID to get specific daily log records.

Instructions

Returns all Inspection 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}/inspection_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__location_idNoQuery string parameter — return item(s) with the specified Location 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 read-only, idempotent, non-destructive behavior. The description adds value by detailing pagination, default date behavior, and response format (paginated JSON array with metadata), which enhances transparency.

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 informative but slightly verbose. It starts with the main action, then covers filtering, usage, pagination, required params, and API reference in a logical order. Could be tightened but is reasonably structured.

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 no output schema, the description adequately describes the return type (paginated JSON array with metadata) and covers filtering, pagination, and required parameters. The link to documentation compensates for missing field details.

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%, so parameters are well-documented. The description adds marginal value by explaining the default date behavior and linking to further documentation, but does not provide significant additional semantics.

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 states 'Returns all Inspection Logs for the current date' and explains it enumerates Daily Log records. It clearly identifies the resource and verb but lacks explicit differentiation from sibling log-listing tools (e.g., list_accident_logs).

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 mentions when to use it (paginated overview, find IDs, filter) and notes default behavior. However, it does not provide exclusions or alternatives, leaving the agent to infer when not to use this tool.

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