Skip to main content
Glama
TylerIlunga

Procore MCP Server

Search All Equipment (Deprecated)

search_all_equipment_project

Search and list equipment details for a specified project, with filters for status, ownership, vendor, or keyword. Returns paginated results.

Instructions

Return a list of all searched equipment with details for a specified project. DEPRECATED: Procore has deprecated this endpoint (as of 2024-12-01). It is scheduled for removal on 2025-12-02; prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it. project_id defaults to the value set by procore_set_config when omitted. Acts on the equipment and returns Procore's response for the operation. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id. Procore API: Project Management > Field Productivity. Endpoint: POST /rest/v1.0/projects/{project_id}/managed_equipment/search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
filters__yearNoQuery string parameter — return item(s) with the specified year.
search_keywordNoQuery string parameter — search keyword to search Project Managed Equipment.
filters__onsiteNoQuery string parameter — onsite Dates. Returns item(s) with the specified range of onsite dates.
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__offsiteNoQuery string parameter — offsite Dates. Returns item(s) with the specified range of offsite dates.
filters__ownershipNoQuery string parameter — returns only item(s) with the specified ownership value. Must be one of Owned, Rented, or Sub.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor ID.
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__company_visibleNoQuery string parameter — if true, return item(s) with 'company visible' status.
filters__induction_statusNoQuery string parameter — returns item(s) with the specified inudction status.
filters__last_service_dateNoQuery string parameter — return item(s) with a last service date within the specified ISO 8601 datetime range.
filters__next_service_dateNoQuery string parameter — return item(s) with a next service date within the specified ISO 8601 datetime range.
filters__current_project_idNoQuery string parameter — return item(s) with the specified current project ID.
filters__managed_equipment_idNoQuery string parameter — return item(s) with the specified Managed Equipment ID.
filters__managed_equipment_make_idNoQuery string parameter — return item(s) with the specified Managed Equipment Make ID.
filters__managed_equipment_type_idNoQuery string parameter — return item(s) with the specified Managed Equipment Type ID.
filters__managed_equipment_model_idNoQuery string parameter — return item(s) with the specified Managed Equipment Model ID.
filters__managed_equipment_category_idNoQuery string parameter — return item(s) with the specified Managed Equipment Category ID.
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it details error payload structures with common HTTP statuses (401, 403, 404), explains the default behavior for project_id, and includes the deprecation timeline. Annotations provide some hints, but the description enriches with specific operational details. 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.

Conciseness4/5

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

The description is moderately long but each sentence serves a purpose: purpose, deprecation, default behavior, error handling, required params, and API reference. It is front-loaded with the core function. While not as terse as possible, the density is justified given the deprecation and operational context.

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?

With 21 parameters and no output schema, the description provides essential context: endpoint URL, error semantics, project_id default, and deprecation guidance. It does not explain pagination or return structure in detail, but the schema covers pagination params and the first sentence states the return type. Overall, it is adequate for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (all parameters have descriptions), so the baseline is 3. The description adds valuable semantic info for project_id, stating that it 'defaults to the value set by procore_set_config when omitted,' which is not in the schema. It also highlights project_id as required, reinforcing schema. This extra context justifies a 4.

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's function: 'Return a list of all searched equipment with details for a specified project.' It specifies the resource (equipment), the scope (project), and the operation (search/list). It also prominently announces the deprecation status, which is critical for selection. This distinguishes it from company-level search tools and other list endpoints.

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 warns against using this tool by noting it is deprecated and scheduled for removal, and instructs to 'prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it.' This provides a clear when-not-to-use and an alternative discovery method. However, it does not elaborate on positive use cases or contrast with non-deprecated siblings.

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