Skip to main content
Glama
TylerIlunga

Procore MCP Server

List All Equipment Logs (Deprecated)

list_all_equipment_logs
Read-onlyIdempotent

Fetch all equipment logs from projects the user can access, with pagination support. Use it to discover equipment logs or locate their IDs for other Procore tools.

Instructions

Return a list of all equipment Logs for the projects the current user has access to. 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. Use this to discover equipment logs or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of equipment logs; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. 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: company_id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/companies/{company_id}/managed_equipment_logs

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)
company_idYesURL path parameter — unique identifier for the company.
Behavior5/5

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

Beyond annotations, the description discloses read-only behavior, pagination behavior, company_id defaulting, and common error statuses (401, 403, 404). This is rich, useful context with no contradiction to annotations.

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

Conciseness5/5

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

Every sentence adds value: purpose, deprecation, usage, defaults, return type, read-only claim, error handling, and API endpoint. It is structured and information-dense without fluff.

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

Completeness5/5

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

For a list tool with no output schema, the description covers return format, pagination, error cases, required parameters, and deprecation status. It gives the agent all necessary context to invoke and interpret results correctly.

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 already provides 100% coverage with descriptions for all three parameters. The description adds context on company_id defaulting to procore_set_config and clarifies pagination semantics, going 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 first sentence clearly states the tool returns a list of equipment logs for accessible projects. The deprecation notice and endpoint details further distinguish it from sibling tools like list_equipment_logs or list_project_equipment_logs.

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

Usage Guidelines5/5

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

Explicitly states when to use (discover logs, look up IDs) and when not to use (deprecated, prefer newer version via procore_search_endpoints). This is strong guidance for tool selection.

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