rotate_webhook_secretReplace a webhook signing secret. The new secret is shown only in this response; update the receiver before relying on further deliveries.
| 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 webhook and its newly rotated 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 destructiveHint=true and non-idempotency, but the description adds a crucial non-obvious behavior: the new secret is visible only in this response, and deliveries may fail until the receiver is updated. That is exactly the operational consequence an agent needs beyond structured hints.
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?
Two sentences, zero filler, and the core action is front-loaded ahead of the operational warning.
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?
With an output schema present, return structure needn't be explained, and the key behavioral risk is covered. Minor omissions like immediate invalidation of the old secret or required permissions keep it from a 5.
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 coverage is 50%, and organization_id is well documented in the schema while webhook_id is self-evident from name and uuid format. The description adds no parameter-level meaning, so the baseline 3 is appropriate rather than compensating further.
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 ('Replace a webhook signing secret'), which is distinct from create_webhook, delete_webhook, and test_webhook by name alone. It does not explicitly contrast with siblings, so it stops short of a 5.
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?
There is no guidance on when to rotate versus creating a new webhook, who may do it, or what preconditions exist. The sentence about updating the receiver is post-invocation operational advice, not when-to-use guidance.
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.