teamgrid_webhook_get is a read-only TeamGrid MCP tool. It is advertised in: all, governance, full, integrations-write.
Get a webhook
Arguments at a glance
The table describes full. When a profile variant is shown below, use that variant’s exact schema.
| Argument | Presence | Type | Meaning |
|---|---|---|---|
id |
Required | string | See the exact schema below for values and constraints. |
Input schema
Stable release: this is the exact JSON Schema advertised by @teamgrid/mcp-server@1.2.2:
{
"type": "object",
"properties": {
"id": {
"maxLength": 128,
"minLength": 1,
"type": "string"
}
},
"required": [
"id"
],
"additionalProperties": false
}The schema above is for full. Properties not in the selected profile schema are rejected.
Input in all
{
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 128
}
},
"required": [
"id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Input in governance
{
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 128
}
},
"required": [
"id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Scope and API operation
Required scopes (all): webhooks:read.
getWebhook—GET /webhooks/{id}
The credential must also satisfy normal workspace authorization and any service-account resource grants. Selecting an MCP tool profile never adds scopes to a credential.
Read behavior
This tool does not change business state.
Output and limits
The bounded API result is returned as MCP structured content and equivalent JSON text. This tool returns a single API response envelope and is not paginated. The serialized result may not exceed 256 KiB.
Additional output boundary:
- Webhook read responses do not contain the reveal-once signing secret.
Download the exact MCP input and output contract, including profile variants, scopes and safety annotations. Its outputSchema describes the advertised MCP envelope and local $defs; it includes MCP projection metadata in addition to the underlying API schema.
The linked API operation describes the business resource and its field semantics. Write tools preserve their declared revision/idempotency contract and require current permissions. Accepted jobs provide status/resume information; uncertain writes must not be replayed blindly.
Security classification
security-configuration: Webhook configuration is security-sensitive. Read responses do not expose the signing secret.
The exact safety annotations are {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}. The host and model can still retain tool
arguments and results in prompts, logs, or transcripts; use a dedicated least-privilege credential.
Example prompt
Read the TeamGrid webhook with ID
<id>and summarize only the fields returned by TeamGrid.
The prompt is illustrative. Inspect the proposed tool arguments before approving access to personal, commercial, conversation, or security-configuration data.
Common failures
| Condition | Observable behavior and recovery |
|---|---|
The selected tool profile or allow/deny filter excludes teamgrid_webhook_get. |
The tool is not advertised to the host. Select the narrowest profile that contains it and restart the host. |
id is missing or violates this tool’s exact input schema, including any pattern or length restriction. |
MCP input validation rejects the call before an API request is made. |
The credential lacks webhooks:read or cannot access the requested resource. |
The tool preserves a safe API error code such as insufficient_scope, with redacted detail and available status/request metadata. |
| A read exceeds the 256 KiB tool result limit. | Use a bounded section, smaller supported read, private resource or authorized App/CLI transfer. |
| An unknown input property is supplied. | The strict input schema rejects the call before an API request is made. |
Authentication failures that prevent the MCP process from starting are covered separately in MCP troubleshooting.