Skip to main content
Glama
TylerIlunga

Procore MCP Server

List RFIs

list_rfis
Read-onlyIdempotent

Retrieve a paginated list of RFIs for a project, with filtering by status, assignee, date, and more. Use this tool to find specific RFI records or IDs.

Instructions

Returns all RFIs in a specified Project. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate RFI records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of RFI records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > RFI. Endpoint: GET /rest/v1.0/projects/{project_id}/rfis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path 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)
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__statusNoQuery string parameter — return item(s) with the specified RFI Status.
filters__assigned_idNoQuery string parameter — filter results by assigned id
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__responsible_contractor_idNoQuery string parameter — array of Responsible Contractor IDs. A single Responsible Contractor ID is also accepted.
filters__cost_code_idNoQuery string parameter — cost Code ID. Returns item(s) with the specified Cost Code ID or within the specified range of Cost Code IDs.
filters__received_from_login_information_idNoQuery string parameter — received From Login Information ID. Returns item(s) with the specified Received From Login Information ID.
filters__ball_in_court_idNoQuery string parameter — user ID. Return item(s) where the specified User ID is the Ball in Court.
filters__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__updated_atNoQuery string parameter — return item(s) last updated 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 `YYY...
filters__rfi_manager_idNoQuery string parameter — return item(s) with the specified RFI Manager ID.
filters__numberNoQuery string parameter — return item(s) with the specified RFI Number.
filters__prefix_stage_idNoQuery string parameter — return item(s) with the specified RFI Prefix Stage.
searchNoQuery string parameter — search for RFIs by subject or number. This parameter will return all RFIs that match the search term.
sort__attributeNoQuery string parameter — the attribute by which to sort the list of RFIs
sort__directionNoQuery string parameter — if passed a sort attribute, determines which direction to sort
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context about pagination and required parameters, but does not significantly extend behavioral disclosure beyond what annotations provide.

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 front-loaded with the main purpose and use cases, followed by technical details like pagination and API endpoint. It is efficient and avoids unnecessary fluff.

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?

With 19 parameters and no output schema, the description covers purpose, pagination, and required parameters. However, it does not describe the structure of the returned RFI records, which could be useful 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?

The schema covers 100% of parameters with descriptions. The description highlights that project_id is required and mentions page/per_page for pagination, but this adds minimal value beyond the schema.

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?

The description clearly states the tool returns all RFIs in a specified project and provides specific use cases like enumeration, ID finding, and filtering. This distinguishes it from sibling tools such as create_rfis or update_rfis.

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 explicitly states when to use this tool (paginated overview, find IDs, filter by query parameters) and mentions filtering capabilities via a documentation link. However, it does not explicitly say when not to use it or suggest 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