Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Equipment Ids By Project (Project)

get_equipment_ids_by_project_project
Read-onlyIdempotent

Fetch equipment IDs for a project with filters and pagination. Use this to retrieve lists of equipment records by specifying project, company, and optional search, filter, and sort parameters.

Instructions

Get equipment ids by project (Project). Use this to fetch the full details of a specific Equipment records by its identifier. Returns a paginated JSON array of Equipment records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id, per_page, company_id. Procore API (v2.1): Core > Equipment. Endpoint: GET /rest/v2.1/companies/{company_id}/projects/{project_id}/equipment_register/ids

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — the Id of the project
company_idYesURL path parameter — unique identifier for the company.
searchNoQuery string parameter — search criteria applied on name, identification number and serial number
filters__idNoQuery string parameter — filter results by id
filters__association_statusNoQuery string parameter — the status of association. Values can be 'current', 'past' or 'all'. Default is 'current'
filters__typeNoQuery string parameter — filter results by type
filters__categoryNoQuery string parameter — filter results by category
filters__makeNoQuery string parameter — filter results by make
filters__modelNoQuery string parameter — filter results by model
filters__type_idsNoQuery string parameter — filter results by type ids
filters__category_idsNoQuery string parameter — category filter by Ids
filters__make_idsNoQuery string parameter — filter results by make ids
filters__model_idsNoQuery string parameter — filter results by model ids
filters__yearNoQuery string parameter — filter results by year
filters__statusNoQuery string parameter — filter results by status
filters__ownershipNoQuery string parameter — filter results by ownership
filters__vendor_idsNoQuery string parameter — filter results by vendor ids
filters__group_idsNoQuery string parameter — filter results by group ids
filters__is_current_projectNoQuery string parameter — flag to filter by current project
filters__assignee_idsNoQuery string parameter — filter results by assignee ids
filters__updated_atNoQuery string parameter — updated at filter (date range format: YYYY-MM-DD...YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ...YYYY-MM-DDTHH:MM:SSZ)
pageNoQuery string parameter — the page number to retrieve. Default is 1.
per_pageYesQuery string parameter — number of records per page
sortNoQuery string parameter — equipment sort. Also supports custom field sorting like 'custom_field_123' or '-custom_field_123' for descending
Behavior2/5

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

Annotations indicate readOnlyHint=true, which is consistent. However, the description claims the tool returns 'full details of Equipment records', but the endpoint '/equipment_register/ids' suggests it returns only IDs. This misleading claim about output behavior reduces transparency. No mention of pagination metadata or rate limits.

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

Conciseness3/5

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

The description is 4 sentences, but includes contradictory and non-essential details (API version, endpoint path). Could be more concise without the misleading statement about 'full details'. Front-loads the name but loses clarity later.

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

Completeness2/5

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

Given 24 parameters and no output schema, the description should clarify that the tool returns equipment IDs (not full details) and explain pagination metadata. It fails to do so and misleads about the output. Annotations cover safety, but the description is incomplete and partially incorrect.

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 baseline is 3. The description adds context about pagination (page, per_page) and lists required parameters, but does not elaborate on filter parameters beyond what the schema provides. Adequate but not exceptional.

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

Purpose3/5

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

The title and first sentence clearly state 'Get equipment ids', but the description then says 'fetch the full details of a specific Equipment records', which is contradictory and confusing. The purpose is somewhat clear but undermined by this inconsistency.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states 'Use this to fetch the full details...' which is misleading. It does not provide guidance on when to use this tool versus alternatives like get_all_equipment_ids_company or get_equipment_by_id. No exclusions or context for alternative tools are mentioned.

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