Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company Webhooks Hooks

list_company_webhooks_hooks
Read-onlyIdempotent

Retrieve a paginated list of company webhooks. Filter by namespace, payload version, or trigger count, and control pagination with page and per_page parameters.

Instructions

Returns an array of webhooks for the company. 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: company_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: GET /rest/v2.0/companies/{company_id}/webhooks/hooks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
namespaceNoQuery string parameter — hook namespace to query.
payload_versionNoQuery string parameter — payload version for the hook
include_trigger_countNoQuery string parameter — include trigger count in the hook response
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the description's behavioral transparency is mainly additive. The description confirms the read-only nature and adds output format details (paginated JSON array, metadata), but does not go beyond annotations significantly.

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 concise (4 sentences) and well-structured, with purpose first, then usage, then output, then details. No redundant information, every sentence adds value.

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?

Given no output schema, the description adequately explains the return type (paginated JSON array of webhooks) and mentions pagination metadata. It could detail the webhook object fields, but for a list tool with rich annotations, it is sufficiently 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?

Schema coverage is 100%, so baseline is 3. The description adds context that company_id is a required URL path parameter and explains pagination parameters (page, per_page) and metadata. This reinforces but does not add new meaning beyond the schema 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 clearly states the tool returns an array of webhooks for the company, with specific use cases like paginated overview, finding IDs, and filtering. It effectively distinguishes from sibling tools (create/delete/update hooks) by focusing on enumeration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (enumerating webhooks, paginated overview, filtering), but does not explicitly state when not to use it or mention alternatives. However, for a list tool, the guidance is adequate.

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