Skip to main content
Glama

RedReplier

Enable Keyword

enable_keyword
DestructiveIdempotent

Enable an existing keyword within the current plan. It becomes ACTIVE if there is capacity, otherwise PENDING; this tool never charges or upgrades a subscription. An already active keyword is returned unchanged. Monitoring alerts are synchronized when activated. No historical backfill runs on re-enable; new matches arrive through monitoring. Use add_keywords for a new keyword.

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": "enable_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordIdYesKeyword to turn back on, by its id from the keywords list in list_websites or get_website, not its text
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. Changed7 schema fields changed
    • changedInput schema / properties / keywordId / description
      Previous value: -"ID of a DISABLED or PENDING keyword to turn on, from the keywords list in list_websites or get_website (the id field, not the keyword text)"New value: +"Keyword to turn back on, by its id from the keywords list in list_websites or get_website, not its text"
    • addedOutput schema / properties / result / properties / createdAt / description
      Added value: +"When the keyword was added, ISO 8601"
    • removedOutput schema / properties / result / properties / updatedAt / $ref
      Removed value: -"#/properties/result/properties/createdAt"
    • addedOutput schema / properties / result / properties / updatedAt / description
      Added value: +"When the keyword last changed, ISO 8601"
    • addedOutput schema / properties / result / properties / updatedAt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / result / properties / websiteId / description
      Added value: +"Website this keyword belongs to"
    • changedOutput schema / properties / result / required
      Previous value: -[
      -  "id",
      -  "websiteId",
      -  "value",
      -  "status"
      -]New value: +[
      +  "id",
      +  "websiteId",
      +  "value",
      +  "status",
      +  "createdAt",
      +  "updatedAt"
      +]
  2. Changed8 schema fields changed
    • changedInput schema / properties / keywordId / description
      Previous value: -"Keyword ID (UUID)"New value: +"ID of a DISABLED or PENDING keyword to turn on, from the keywords list in list_websites or get_website (the id field, not the keyword text)"
    • addedInput schema / properties / keywordId / format
      Added value: +"uuid"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"The keyword with status ACTIVE, or PENDING when the plan has no free slot for it."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "createdAt": {
      +    "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": {
      +    "$ref": "#/properties/result/properties/createdAt"
      +  },
      +  "value": {
      +    "description": "Lowercased keyword text, the value list_mentions filters on",
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "id",
      +  "websiteId",
      +  "value",
      +  "status"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  3. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Changed1 schema field changed
    • 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"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / properties / result / description
      Previous value: -"The keyword with status ACTIVE, or PENDING when an upgrade was charged and its payment has not settled yet."New value: +"The keyword with status ACTIVE, or PENDING when the plan has no free slot for it."
  6. Changed1 schema field changed
    • changedOutput schema / properties / result / description
      Previous value: -"The keyword with its resulting status (ACTIVE or PENDING)."New value: +"The keyword with status ACTIVE, or PENDING when an upgrade was charged and its payment has not settled yet."
  7. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the resulting state transition (ACTIVE if capacity, else PENDING), states no charge or upgrade occurs, confirms idempotency for already-active keywords, and notes that alerts are synchronized and no historical backfill runs. These are exactly the side-effect facts an agent needs before invoking a mutating tool. The only tension is with destructiveHint=true, which the description does not obviously justify, but that is an annotation oddity rather than a contradiction of stated behavior.

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?

Five short sentences, each carrying a distinct fact: state outcome, billing boundary, idempotency, alert sync, no backfill, and the sibling alternative. The outcome and the no-charge guarantee are front-loaded where an agent will read them first.

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?

An output schema exists, so return shape need not be explained, and the annotations carry the safety profile. For a two-parameter state-toggle tool the description covers outcome, cost, idempotency, monitoring side effects, and the alternative, leaving nothing material unstated.

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%, with keywordId and workspaceId fully described in the schema itself, so the baseline is 3. The description adds only the qualifier "existing" and reinforces that the target is a keyword within the current plan, without adding format, sourcing, or workspace-scoping detail 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?

Opens with a specific verb+resource ("Enable an existing keyword") and scopes it to "the current plan." It also implicitly distinguishes itself from add_keywords and disable_keyword by naming the create case as a sibling concern, so an agent can pick it without opening another 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?

Explicitly routes the new-keyword case to add_keywords and states the already-active case is a no-op, which tells the agent this is safe to retry. It gives no guidance on the converse cases (disable_keyword vs delete_keyword) or on preconditions such as plan capacity, leaving some inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources