Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Webhooks Triggers

list_webhooks_triggers
Read-onlyIdempotent

List paginated webhook triggers for a specific hook within a company or project. Use to find trigger IDs or filter by query parameters.

Instructions

Triggers must be listed within a company and/or project scope. Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Webhooks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: hook_id, company_id, project_id. Procore API: Platform - Developer Tools > Webhooks. Endpoint: GET /rest/v1.0/webhooks/hooks/{hook_id}/triggers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hook_idYesURL path parameter — unique identifier of the hook
company_idYesQuery string parameter — unique identifier for the company. You must supply either a company_id or project_id.
project_idYesQuery string parameter — unique identifier for the project. You must supply either a company_id or project_id.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/5

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

The description adds context about pagination and API reference, but the contradictory required parameters (schema requires both company_id and project_id while description says either/or) is a significant transparency issue that misleads the agent. Annotations already declare safe behavior.

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?

The description is concise at 5 sentences and front-loads key constraints, but the presence of contradictory information reduces its overall effectiveness. It could be improved by resolving the inconsistency.

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?

The description covers purpose, pagination, required params, and API reference. However, it fails to explain the behavior when both company_id and project_id are provided, and does not contextualize the sibling tools. No output schema exists, so more detail on return values would help.

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%, so baseline is 3. The description adds that page/per_page control pagination and response includes metadata, which provides some value. However, the contradiction regarding company_id and project_id requirement undermines clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists webhooks triggers with pagination and scope constraints. However, it fails to distinguish from sibling tools like list_company_webhooks_triggers and list_project_webhooks_triggers, and the contradictory requirement of both company_id and project_id vs either/or reduces clarity.

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?

The description suggests using it for paginated overview, finding IDs, or filtering, but does not specify when not to use it or alternatives. It lacks exclusion guidance relative to the more specific company/project 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