Skip to main content
Glama
Sign In

MentionAgent

by ai.mentionagent
OverviewDiscussionsAdmin

Remove search keywords

remove_keywords
DestructiveIdempotent

Stop discovery running these searches. Exact text, as list_keywords shows it; to stop a whole kind of site ('no directories') use plan_campaign_change instead. Removed keywords are kept as history so they are not generated again. The pool never drops below the minimum a run needs. Up to 25 per call.

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": {
      "workspaceId": "<workspaceId>",
      "keywords": "<keywords>"
    },
    "name": "remove_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesExact keyword text from list_keywords.
workspaceIdYesWhich site to act on. Call get_status with no arguments to list them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds non-obvious behavior: removed keywords are retained as history so they are not regenerated, the pool will not fall below the minimum a run needs, and there is a 25-per-call cap. These are substantive operational facts beyond the structured hints.

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, no filler; the primary action and the routing alternative are front-loaded before the secondary facts about history retention, pool floor, and batch size. Every sentence carries distinct information.

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

Completeness4/5

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

For a 2-parameter mutation tool with no output schema, the description covers alternatives, batch limits, and retention behavior. It is slightly thin on edge cases (unknown keyword text, partial failure reporting), but annotations already carry the destructive/idempotent profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds one genuine constraint not present in the schema — 'Up to 25 per call' on the keywords array — while the 'exact text from list_keywords' guidance only restates the schema wording.

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?

Starts with a concrete verb+resource (stop discovery running these searches) and immediately distinguishes itself from sibling tools by naming plan_campaign_change for the broader 'no directories' case. An agent can tell this apart from add_keywords/list_keywords 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 this for exact keyword text (as list_keywords shows it), use plan_campaign_change to stop an entire kind of site. Both the alternative and the condition that selects it are stated, so nothing is left to inference.

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

All MentionAgent 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