Skip to main content
Glama
TylerIlunga

Procore MCP Server

Discover Endpoints in a Category

procore_discover_endpoints
Read-onlyIdempotent

Discover Procore API endpoints by category or module, and filter by summary text or HTTP method to narrow results. Returns operationId, method, path, and summary for each endpoint.

Instructions

Lists the Procore endpoints inside one category or module, optionally narrowed by a summary substring or HTTP method. Use it after procore_discover_categories to enumerate a focused area; prefer procore_search_endpoints when you have a keyword but no category. Every argument is optional, but omitting all of them returns the entire ~3,100-endpoint catalog, so pass at least a category or a search term. Returns a JSON array of {operationId, summary, method, path}; feed an operationId to procore_get_endpoint_details. Filters that match nothing return an empty array, not an error. Reads the bundled catalog: no Procore request, no authentication, no rate-limit cost. Step 2 of the workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleNoModule within the category, e.g. 'RFI', 'Submittals', 'Punch List'. Ignored unless category is also given.
searchNoCase-insensitive substring matched against endpoint summary text; combine with category to narrow a large module
categoryNoTop-level category, exactly as returned by procore_discover_categories, e.g. 'Project Management', 'Core', 'Construction Financials'
method_filterNoRestrict results to a single HTTP method — useful to list only the reads (GET) in a module

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / category / description
      Previous value: -"Top-level category, e.g. 'Project Management', 'Core', 'Construction Financials'"New value: +"Top-level category, exactly as returned by procore_discover_categories, e.g. 'Project Management', 'Core', 'Construction Financials'"
    • changedInput schema / properties / method_filter / description
      Previous value: -"Restrict results to a single HTTP method"New value: +"Restrict results to a single HTTP method — useful to list only the reads (GET) in a module"
    • changedInput schema / properties / module / description
      Previous value: -"Module within the category, e.g. 'RFI', 'Submittals', 'Punch List'"New value: +"Module within the category, e.g. 'RFI', 'Submittals', 'Punch List'. Ignored unless category is also given."
    • changedInput schema / properties / search / description
      Previous value: -"Substring filter applied to endpoint summary text"New value: +"Case-insensitive substring matched against endpoint summary text; combine with category to narrow a large module"
  2. Changed3 schema fields changedv1.1.0
    • changedInput schema / properties / method_filter / description
      Previous value: -"Filter by HTTP method"New value: +"Restrict results to a single HTTP method"
    • changedInput schema / properties / module / description
      Previous value: -"Module within category, e.g. 'RFI', 'Submittals', 'Punch List'"New value: +"Module within the category, e.g. 'RFI', 'Submittals', 'Punch List'"
    • changedInput schema / properties / search / description
      Previous value: -"Filter endpoints by summary text"New value: +"Substring filter applied to endpoint summary text"
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already state readOnly, idempotent, and non-destructive, and the description adds key behavioral context: it reads a bundled catalog, makes no network request, requires no authentication, and has no rate-limit cost. It also discloses the full-catalog fallback when all arguments are omitted and the empty-array behavior for no matches, going well beyond the structured 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?

The description is slightly long but every sentence earns its place: it covers purpose, workflow placement, sibling alternatives, argument warnings, return format, error behavior, and cost implications. It is front-loaded with the main action and then provides structured detail without redundancy or padding.

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?

With no output schema, the description clearly states the return shape (JSON array of {operationId, summary, method, path}) and how to chain the result into procore_get_endpoint_details. It also documents the no-match empty-array behavior, the unbounded result risk, and the read-only/local nature, making the tool fully understandable for a four-optional-parameter, no-output-schema tool.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful parameter relationships not in the schema: module is ignored unless category is also given, all arguments are optional but at least one is recommended, and combining category with search narrows a large module. These extra constraints and usage hints improve parameter understanding beyond the field descriptions.

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 opens with a specific verb ('Lists') and a clear resource ('Procore endpoints inside one category or module'), with optional narrowing by summary substring or HTTP method. It explicitly distinguishes itself from siblings by directing users to procore_search_endpoints when they have a keyword but no category, and to pass operationIds to procore_get_endpoint_details.

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?

The description gives explicit when-to-use guidance: use after procore_discover_categories, prefer procore_search_endpoints for keyword-only searches, and avoid calling with no arguments because it returns the entire ~3,100-endpoint catalog. It also explains filter behavior (empty array on no match) and that it reads the bundled catalog, so it is the right choice when avoiding API cost.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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