Skip to main content
Glama
TylerIlunga

Procore MCP Server

List All Maintenance Logs Attachment

list_all_maintenance_logs_attachment
Read-onlyIdempotent

Retrieve a paginated list of all attachments for a specific maintenance log by providing company ID and maintenance log ID. Control pagination with page and per_page parameters.

Instructions

Return a list of all Maintenance Log attachments for the Maintenance Log the current user has access to. Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Field Productivity records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/companies/{company_id}/managed_equipment_maintenance_logs/{id}/attachments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Field Productivity resource
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Beyond annotations (readOnlyHint, etc.), the description adds pagination behavior, response format (JSON array with metadata), and endpoint details. No contradictions 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.

Conciseness3/5

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

Description is front-loaded with purpose but mixes 'maintenance log attachments' and 'Field Productivity records', causing slight confusion. Could be more concise by using consistent terminology.

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?

No output schema, so description must explain return values. It states a paginated JSON array with metadata, but the ambiguous resource type ('Field Productivity records' vs attachments) reduces completeness.

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% with parameter descriptions. The description restates required params and pagination usage, but does not add substantial new meaning beyond reinforcing 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?

Description states it returns a list of maintenance log attachments, which is clear. However, it also mentions 'Field Productivity records' which may cause confusion about the exact resource. Still, the verb 'list' and resource are identifiable.

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?

Provides usage context (paginated overview, find IDs, filter) and required parameters, but does not explicitly differentiate from sibling tools like show_an_individual_managed_equipment_maintenance_log_attachment or mention when not to use.

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