Skip to main content
Glama

tumblr_guide

Get guidance on Tumblr screens and the sign-in link for managing posts, queues, drafts and asks. Call this first before other Tumblr actions.

Instructions

How to work in Tumblr (manage blog posts, queues, drafts and asks): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tumblr_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Tumblr, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose the kind of content returned (screens and the sign-in link) and the required call ordering, but it never states whether invoking it has side effects, whether it requires an existing session, or what the response looks like.

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?

Two short clauses with the imperative 'Call this first' front-loaded at the end for emphasis; no wasted wording. The parenthetical list is dense but readable.

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 simple, single-optional-parameter guide tool with no output schema, the description covers what it is and when to call it. Minor gaps remain around session/auth implications and how to use the returned sign-in link, but nothing critical for correct invocation.

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?

The single 'task' parameter has 100% schema description coverage, so the schema already explains it. The description adds no guidance on how to phrase the task or whether it changes the guide returned, which is the baseline-3 outcome when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific role: a guide to working in Tumblr covering screens, posts/queues/drafts/asks, and the sign-in link. It distinguishes itself from the sibling UI primitives (click, open, read, type) by being orientation rather than an action, though 'How to work in Tumblr' is slightly abstract and doesn't explicitly say it returns documentation versus performing navigation.

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?

'Call this first' gives explicit ordering guidance that an agent can act on, which is the key usage decision for an orientation tool. It stops short of saying whether it should be re-called per session or how it relates to subsequent tumblr_open/tumblr_click calls.

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