Skip to main content
Glama

Disable Keyword

disable_keyword
DestructiveIdempotent

Pauses one keyword so it stops matching new mentions while keeping its stored mentions and alert sync intact. Frees a plan slot without changing your subscription.

Instructions

Set one keyword to DISABLED and stop matching new mentions. Keeps its stored mentions and synchronizes monitoring alerts. Use enable_keyword to resume monitoring within the current entitlement, or delete_keyword to permanently erase the keyword and its mentions. Disabling an active keyword frees a plan slot, so the oldest pending keyword that now fits the plan may become active, which queues public-network searches and ranking checks. An already disabled keyword is returned unchanged. This tool does not charge, refund, or change the subscription.

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": {
      "keywordId": "<keywordId>"
    },
    "name": "disable_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordIdYesID of the keyword to pause, from the keywords list in list_websites or get_website
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / keywordId / description
      Previous value: -"Keyword ID (UUID)"New value: +"ID of the keyword to pause, from the keywords list in list_websites or get_website"
    • addedInput schema / properties / keywordId / format
      Added value: +"uuid"
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"The keyword with status DISABLED; its paid slot is held until the billing cycle ends."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "createdAt": {
      +    "description": "When the keyword was added, ISO 8601",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "id": {
      +    "description": "Keyword ID for edit_keyword, enable_keyword, disable_keyword and delete_keyword",
      +    "type": "string"
      +  },
      +  "status": {
      +    "description": "PENDING (saved, not monitored until the plan covers it), ACTIVE, DISABLED or SUSPENDED",
      +    "type": "string"
      +  },
      +  "updatedAt": {
      +    "description": "When the keyword last changed, ISO 8601",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "value": {
      +    "description": "Lowercased keyword text, the value list_mentions filters on",
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "description": "Website this keyword belongs to",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "id",
      +  "websiteId",
      +  "value",
      +  "status",
      +  "createdAt",
      +  "updatedAt"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed1 schema field changedv0.1.1
    • changedOutput schema / properties / result / description
      Previous value: -"The keyword with its status set to DISABLED."New value: +"The keyword with status DISABLED; its paid slot is held until the billing cycle ends."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/openWorld/idempotent) by disclosing that mentions are retained, alerts are synchronized, a plan slot is freed which may auto-activate the oldest pending keyword and queue public-network searches and ranking checks, that an already-disabled keyword is returned unchanged, and that no billing changes occur. This is exactly the side-effect detail an agent needs before a destructive-flagged call.

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?

Front-loads the core action, then alternatives, then side effects, then a billing disclaimer. Sentences are dense but each carries a distinct, useful fact with no repetition.

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?

With an output schema present and annotations covering safety, the description fills the remaining gaps: side effects on plan slots, cascading keyword activation, idempotent behavior, and billing neutrality. Nothing an agent needs in order to call it correctly 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 description coverage is 100%, so the schema already explains keywordId and workspaceId thoroughly; the description only reinforces that exactly one keyword is affected. Baseline 3 is appropriate since it adds little parameter-level meaning beyond the schema.

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 ('Set one keyword to DISABLED and stop matching new mentions') and immediately contrasts with enable_keyword and delete_keyword, so the agent can distinguish it from siblings without opening a schema.

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?

Explicitly routes the agent: use enable_keyword to resume monitoring, delete_keyword to permanently erase. Conditions are concrete and cover the main alternative actions an agent might otherwise confuse with disabling.

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