Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A New Layer

create_a_new_layer

Create a new layer within a document markup context in Procore. Provide company, project, name, type, and context ID to create the record.

Instructions

Create a new layer within a context. Use this to create a new Document Markup records in Procore. Creates a new Document Markup records and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, name, type, context_id. Procore API: Project Management > Document Markup. Endpoint: POST /rest/v1.0/companies/{company_id}/projects/{project_id}/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
nameYesJSON request body field — the name for this Document Markup operation
typeYesJSON request body field — the type for this Document Markup operation
context_idYesJSON request body field — unique identifier of the context
order_indexNoJSON request body field — the order index for this Document Markup operation
visibilityNoJSON request body field — the visibility for this Document Markup operation
settingsNoJSON request body field — the settings for this Document Markup operation
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds HTTP 201 status but no additional behavioral constraints or side effects.

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?

Concise and front-loaded: states purpose, usage, required params, and API reference in a few sentences. No redundant information.

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?

Sufficient for a create operation with no output schema. Minor gap: does not explain what a 'layer' is or the relationship to 'Document Markup'. But overall adequate.

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?

Input schema has 100% description coverage for all 8 parameters. The description lists required parameters but adds no meaning beyond what's in 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 description clearly states it creates a new layer within a context, specifically for Document Markup records. Among siblings like 'add_a_new_markup' and 'delete_layer', it uniquely identifies the resource and action.

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?

Implied usage from context: use to create layers before adding markups. However, there is no explicit when-not-to-use or comparison with alternatives like 'add_a_new_markup'.

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