unpublish_pageRevoke an exact NotePom public page.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | ||
| idempotencyKey | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | No | ||
| revoked | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already indicate destructiveHint=true and readOnlyHint=false, and the description merely restates the mutation with 'Revoke' without adding behavioral context. It does not explain what happens to the page URL, the listing status, reversibility, or how the idempotency key factors into execution.
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?
The description is a single short sentence with no filler or repetition. The action and target are front-loaded, making the description efficient and easy to parse.
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?
Given that this is a destructive, idempotent mutation with a required idempotencyKey and open-world semantics, the description is too sparse. It omits side effects, prerequisites, and behavioral expectations, leaving the agent to infer critical invocation details.
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 0%, and the description does not compensate. It only vaguely refers to an 'exact' page, without explaining that pageId is the identifier or what idempotencyKey is for, its constraints, or why it is required.
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?
The description states a clear action ('Revoke') and a specific resource ('NotePom public page'), making it evident that this tool unpublishes a page and is likely the inverse of publish_page. However, it does not explicitly differentiate itself from related siblings such as disable_listing or update_public_page.
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 use this tool versus alternatives. An agent is not told what conditions warrant unpublishing, how this differs from disable_listing, or when to choose update_public_page instead.
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.
Most tools target a distinct resource and action, and lifecycle pairs like publish_note_listing vs publish_media_listing or get_note vs get_collaboration_note are separated by clear wording. A few near-pairs such as move_file vs move_workspace_item and trash_file vs trash_workspace_item could still cause an agent to pick the wrong tool without careful reading.
All 38 tools follow one consistent verb_noun snake_case pattern with no camelCase or mixed conventions. Even less common verbs like upsert, trash, purge, and validate are applied uniformly, making the tool set predictable.
38 tools is well above the 25+ threshold and makes the overall surface feel heavy for tool selection. The number is defensible given the broad workspace, collaboration, and marketplace scope, but as a single MCP server it is not especially well-scoped.
The tool set covers workspace content lifecycle, collaboration, public pages, marketplace listings, Stripe seller flow, and agent registration without major dead ends. Minor gaps exist, such as no permanent delete outside of the trash flow and no direct collaboration-note deletion, but core workflows are supported.