Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Witness Statements

list_witness_statements
Read-onlyIdempotent

Retrieve paginated witness statements for a project. Filter by incident, date, witness, or search query to find specific records.

Instructions

Returns a list of Witness Statements for a given project. Use this to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Incidents. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/projects/{project_id}/incidents/witness_statements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
incident_idNoQuery string parameter — incident ID. When provided, the list will be scoped to only the Witness Statements for a given Incident.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__created_atNoQuery string parameter — return item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-...
filters__date_receivedNoQuery string parameter — return item(s) within the specified date received date range. This assumes the dates provided are in the project time zone.
filters__witness_idNoQuery string parameter — return item(s) with the specified Witness (Party) ID.
filters__queryNoQuery string parameter — return item(s) containing query
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
Behavior4/5

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

Annotations already declare it's read-only and idempotent. The description adds useful behavioral details such as pagination control via page/per_page and that the response includes pagination metadata, which is 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 concise with a clear front-loaded purpose. It includes relevant API reference info without being overly verbose, though the mention of 'Incidents' could be removed to avoid confusion.

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 has 9 parameters and no output schema, the description adequately covers the core functionality and pagination. It does not detail the response structure but the schema provides parameter descriptions.

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 the description adds minimal extra meaning. It mentions required project_id and pagination parameters but does not elaborate on filter parameters, which are already well-described in 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 it returns a list of witness statements for a project and identifies use cases like enumeration and filtering. However, it incorrectly mentions 'Incidents' when the tool is for witness statements, causing minor confusion.

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 provides context for when to use the tool (paginated overview, find IDs, filter) but does not specify when not to use it or mention alternative tools like 'show_witness_statement' or 'create_witness_statement'.

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