Skip to main content
Glama
Sign In
Official Porkbun MCP Server

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Revoke Site Share

revoke_site_share
DestructiveIdempotent

Revoke a site share by ID to immediately cut off access: disables an active user's key within seconds or cancels an unused invite link. Confirm with the user first.

Instructions

End a site share by id (from list_site_shares). If the link has not been used, it stops working. If the other person already connected, their key is disabled and their app or agent loses access within seconds. Confirm with the user first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "revoke_site_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe share id from list_site_shares.
dry_runNoShow what would be revoked, without revoking it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.62.0

TDQS

A4.5/5.0
Behavior5/5

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

Although annotations already flag destructiveHint=true and idempotentHint=true, the description adds substantive consequences the annotations cannot convey: an unused link simply stops working, while an already-connected user has their key disabled and loses access 'within seconds.' It also adds the confirmation requirement, which is exactly the kind of operational context the annotations lack.

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?

Three short sentences, each carrying distinct information: what it does, both outcome branches, and the safety instruction. The destructive consequence is front-loaded and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with no output schema, the description covers the identifier source, both possible end states, and the required human confirmation. The only untouched item, dry_run, is fully documented in the schema, so nothing an agent needs is missing.

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 coverage is 100%: the id parameter is already documented as 'The share id from list_site_shares,' and dry_run is described as a preview-only mode. The description's reference to the id source restates the schema rather than adding new meaning, and it does not mention dry_run at all, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource pair ('End a site share') and scopes it to an 'id' sourced from list_site_shares. An agent can immediately distinguish this from share_site_access or list_site_shares without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the prerequisite source for the id (list_site_shares) and adds an explicit procedural instruction, 'Confirm with the user first,' which is genuine when-to-use guidance for a destructive operation. It stops short of naming an alternative tool or stating when not to revoke, so it is clear context rather than a full routing rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools