Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Webhooks Deliveries

list_project_webhooks_deliveries
Read-onlyIdempotent

Retrieve paginated webhook deliveries for a project. Filter by status, resource, event type, or date range. Identify delivery IDs and monitor delivery history.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
hook_idYesURL path parameter — unique identifier of the hook
filter__statusNoQuery string parameter — filter on status
filter__resource_nameNoQuery string parameter — filter on resource_name
filter__event_typeNoQuery string parameter — filter on event_type (create, update, delete)
filter__startNoQuery string parameter — filter deliveries from this date format yyyy-mm-dd
filter__endNoQuery string parameter — filter deliveries until this date format yyyy-mm-dd
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations indicate read-only, non-destructive, idempotent. Description adds value by specifying the HTTP endpoint, pagination metadata, and required parameters, going beyond annotations.

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?

Four sentences, focused and front-loaded with purpose. Includes endpoint detail without being verbose.

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?

Covers pagination and parameters well, but lacks description of delivery object fields. Given no output schema, more detail on response structure would improve completeness.

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. Description adds minimal context (pagination control and required params) but doesn't significantly enhance understanding beyond 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 it returns a paginated array of webhooks deliveries for the project, with filtering capabilities. It distinguishes from company-level siblings by specifying 'for the project', but doesn't explicitly differentiate from other list endpoints.

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?

Provides use cases (enumerate, find IDs, filter) and pagination control, but lacks explicit when-not-to-use or alternative tools among siblings.

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