get_webhookGet a webhook by ID without revealing its signing secret.
| Name | Required | Description | Default |
|---|---|---|---|
| webhook_id | Yes | ||
| organization_id | No | Organization for this operation and billing. Use list_organizations to choose an active membership. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | The requested webhook without its signing secret. |
Changes observed during successful MCP inspections.
Input schema / properties / organization_id / descriptionPrevious value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."Input schema / properties / organization_idAdded value: +{
+ "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / webhook_id / patternAdded value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / result / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / signing_secret / $refRemoved value: -"#/properties/result/properties/study_id"Output schema / properties / result / properties / signing_secret / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / result / properties / updated_at / $refRemoved value: -"#/properties/result/properties/created_at"Output schema / properties / result / properties / updated_at / descriptionAdded value: +"ISO 8601 timestamp."Output schema / properties / result / properties / updated_at / typeAdded value: +[
+ "string",
+ "null"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context by stating the signing secret is withheld from the response, which an agent would otherwise have to infer from the output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no filler, and the key qualifier (secret withheld) is front-loaded. It is arguably too terse rather than too long, which is not a conciseness defect but leaves gaps elsewhere.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Annotations and an output schema carry most of the load, and the redaction note is a useful addition. Still missing is any guidance on choosing this over list_webhooks and any clarification of the organization_id scoping required for a correct call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
schema_description_coverage is 50%: organization_id is documented in the schema (including the list_organizations pointer) but webhook_id has only a format/pattern. The description adds nothing about either parameter, so it does not compensate for the undocumented UUID input.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get a webhook') and scopes it with 'by ID', which implicitly separates it from list_webhooks. It does not explicitly name a sibling alternative, but the ID-based single-resource fetch is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: 'by ID' signals this is for when a webhook identifier is already known, and the sibling list_webhooks covers discovery. No explicit when-to-use or when-not-to-use statement, and no prerequisites such as organization scoping are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.