Skip to main content
Glama
Sign In

Serpier

by com.serpier
OverviewDiscussionsAdmin

remove-seo-keywords

Destructive

Remove tracked SEO keywords by keywordId from get-seo-keywords. Deletes their rank history permanently.

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": {
      "advertiserProjectId": "<advertiserProjectId>",
      "keywordIds": "<keywordIds>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "remove-seo-keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
keywordIdsYesTracked keyword ids from get-seo-keywords to stop tracking.
advertiserProjectIdYesProject id from get-projects or get-project.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the important detail that rank history is deleted permanently, which annotations cannot convey. It stops short of stating whether the delete is all-or-nothing across multiple keywordIds or whether history is recoverable, so not a 5.

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?

Two short sentences, front-loaded with the action and followed by the consequence. Every clause carries information; nothing is redundant or padding.

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 destructive mutation with no output schema and fully documented parameters, the description covers what is removed and that it is irreversible, which is what an agent most needs before calling. Partial-failure behavior and any batch limits on keywordIds remain unstated, a minor gap.

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 all four parameters are documented in the schema itself, establishing the baseline of 3. The description reinforces keywordIds as tracked ids from get-seo-keywords but adds no new constraint such as array size handling or id format 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?

Names the exact action and resource (remove tracked SEO keywords by keywordId) and ties the input source to the sibling get-seo-keywords, distinguishing it from add-seo-keywords. An agent can identify what it does and where the ids come from without opening the 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?

Usage context is clear: ids come from get-seo-keywords, and the permanence sentence signals this is a deliberate cleanup action rather than something routine. It does not explicitly say when NOT to use it (e.g., use update-seo-keyword-tags to stop reporting instead of deleting), which keeps it below a 5.

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

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