Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Layers

get_layers
Read-onlyIdempotent

Retrieve all accessible markup layers (public and private) for a company and project. Supports pagination and filtering by fields like id, created date, or updated date.

Instructions

Returns all accessible markup layers (public + user's private) for a specific company and project with pagination and filtering support. Use this to fetch the full details of a specific Document Markup records by its identifier. Returns a paginated JSON array of Document Markup records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API: Project Management > Document Markup. Endpoint: GET /rest/v1.0/companies/{company_id}/projects/{project_id}/domains/layers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the Procore company
project_idYesURL path parameter — unique identifier for the Procore project
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
viewNoQuery string parameter — response detail level. Use 'normal' for standard fields or 'extended' for all fields
filters__created_beforeNoQuery string parameter — filters[created_before]
filters__updated_atNoQuery string parameter — filter results by updated at
filters__idNoQuery string parameter — filter results by id
filters__context_idNoQuery string parameter — filter results by context id
filters__context_type_idNoQuery string parameter — filters[context_type_id]
filters__subcontext_type_idNoQuery string parameter — filters[subcontext_type_id]
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds useful context: pagination support, returning a paginated JSON array with metadata, and scope (public + user's private layers). This enriches 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.

Conciseness3/5

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

Four sentences with some redundancy: 'Returns a paginated JSON array of Document Markup records' is repeated. The mention of fetching a specific record by identifier seems out of place and adds confusion.

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?

Given no output schema, the description provides a basic return type and pagination metadata. However, it lacks differentiation from siblings (e.g., get_layers_for_context) and does not mention sorting or default pagination values. Adequate but not complete.

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?

Since input schema has 100% coverage and describes each parameter, the description adds 'Use page and per_page to control pagination' which is minimal. Baseline score of 3 is appropriate.

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?

The description clearly states it returns all accessible markup layers for a company/project with pagination and filtering. However, it also says 'Use this to fetch the full details of a specific Document Markup records by its identifier', which is misleading since this is a list tool, not a single-record fetcher.

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?

No explicit guidance on when to use this tool vs alternatives like get_layer_by_id or get_layers_for_context. The mention of fetching a specific record by identifier is incorrect and does not help the agent decide between tools.

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