Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Webhooks Deliveries

list_webhooks_deliveries
Read-onlyIdempotent

List paginated webhook deliveries for a hook, with filters by status. Requires hook_id, company_id, and project_id.

Instructions

Deliveries 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}/deliveries

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.
page_sizeNoQuery string parameter — number of items to return for a page (default: 100)
page_startNoQuery string parameter — the last id of the previous page.
filters__statusNoQuery string parameter — filter on status for "any", "successful", "failing" or "discarded"
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds pagination behavior and return format, enhancing transparency without contradictions.

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), front-loaded with purpose and usage, with no redundant or unnecessary text.

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?

For a list endpoint with no output schema, the description adequately describes the return (paginated JSON array with metadata) and mentions filtering. Could clarify filtering capabilities more.

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 has 100% parameter description coverage. The description adds a summary of required parameters and pagination controls, but adds limited new meaning beyond the schema.

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 the tool lists webhook deliveries with pagination, specifying verb and resource. However, it does not distinguish from sibling tools like list_company_webhooks_deliveries or list_project_webhooks_deliveries, which could cause confusion.

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?

The description explains when to use the tool (enumerate, paginate, filter), but lacks explicit when-not to use and alternatives. Sibling tools are present but not referenced.

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