Skip to main content
Glama
Sign In

ExtensionDash

by io.github.tonic20
OverviewDiscussionsAdmin

Remove extension

remove_extension
DestructiveIdempotent

Stop tracking one of this account's extensions, using an extension_id from list_extensions. Remove only the extension the user asked to remove; clarify ambiguous names first. Never remove an extension automatically to make room at a plan limit.

This deletes this account's extension record, notes, keyword tracking and competitor configuration for it, across both stores. Re-adding does not restore that configuration. Shared store listings, collected metrics/rank history and other users' tracking remain. A missing or already removed id returns the same error as another account's id.

Needs an ExtensionDash account: sign in from your app, e.g. claude mcp login extensions-dashboard or codex mcp login extensions-dashboard.

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": {
      "extension_id": "<extension_id>"
    },
    "name": "remove_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
extension_idYesThe user's chosen extension_id from list_extensions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description goes well beyond them by enumerating the collateral damage (notes, keyword tracking, competitor config, both stores), stating that re-adding does not restore it, and clarifying what survives (shared listings, metrics, other users' tracking). The error-equivalence note for missing versus unauthorized ids is unusual and valuable context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then safety rules, then consequences, then auth. Slightly heavy overall because the login command line is verbose, but every block carries distinct information.

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 single-parameter destructive tool with no output schema, this covers scope, alternatives, destruction radius, irreversibility, error behavior, and auth requirements. Nothing an agent needs in order to call it safely 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% and the single parameter is described there; the description only reinforces the provenance of extension_id from list_extensions. Baseline 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?

States a specific verb and resource ('Stop tracking one of this account's extensions') and immediately ties the identifier to the sibling tool list_extensions, which distinguishes it from add_extension and get_extension.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not-to-use guidance: remove only what the user asked, clarify ambiguous names first, and never remove automatically to free a plan slot. This is exactly the routing guidance a destructive tool needs.

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

All ExtensionDash toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources