Skip to main content
Glama
Sign In

Rankwise

by com.tryrankwise
OverviewDiscussionsAdmin

Add keywords to the planner

add_keywords
Idempotent

Add up to 50 keywords to the Content Planner. Each becomes a card. With a day it takes that day (an unwritten card there moves to the next free day); without one it takes the next free publishing day. Keywords already planned are skipped, so a retry never adds twice. Free: articles are drafted when their day comes.

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

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords as strings, or objects with keyword, day, article_type and article_length.

Output Schema

NameRequiredDescriptionDefault
addedYes
failedYes
skippedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false; the description goes further by explaining *why* it is idempotent ('keywords already planned are skipped, so a retry never adds twice') and by describing the scheduling side effects (day occupancy, unwritten card relocation, next free publishing day). It stops short of permission/auth or rate-limit details, but the annotation bar is already met.

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?

Four tight sentences, front-loaded with the action and cap, then the scheduling rules and idempotency. Slightly telegraphic phrasing ('With a day it takes that day') costs a little clarity but nothing is wasted.

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?

With an output schema present, return values need not be described, and the description covers the mutation's key side effects, limits and retry safety. It could still note whether the caller needs an existing planner or quota, but for a single-parameter tool this is close to complete.

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, but the description adds real meaning: it explains the 50-item cap and, crucially, the semantic difference between supplying a 'day' versus omitting it—a distinction the schema's date pattern alone does not convey.

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 ('Add ... keywords to the Content Planner') and immediately clarifies the effect ('Each becomes a card'), which cleanly separates it from siblings like list_keywords, add_domain and add_question.

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

Usage Guidelines3/5

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

The context for calling it is implied (you want keywords scheduled in the planner) and the day/no-day branching is explained, but the description never names an alternative or states when not to use it (e.g. versus list_keywords or move_planner_card).

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

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