Skip to main content
Glama

tumblr_read

Read the current Tumblr page to extract its text and numbered buttons, links, and fields, optionally limiting the read to a specific element.

Instructions

Read the current Tumblr page: its text and numbered buttons, links and fields.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully enumerates the return shape (text, numbered buttons, links, fields), but says nothing about read-only safety, whether any page state changes, size or truncation limits, or what happens when no page is open.

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?

One compact sentence with the action front-loaded and the output contents following immediately. Nothing is padded, though the terseness leaves no room for prerequisite or edge-case notes.

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

Completeness2/5

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

This is a simple one-parameter tool and there is no output schema, so the description is the only place return values can be explained; it does sketch them, which helps. But for a tool with zero annotation coverage it omits the failure conditions and state assumptions an agent needs before calling.

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% and the single optional 'element' parameter is fully documented in the schema itself. The description adds no scoping or format detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Read the current Tumblr page,' and goes on to name the payload ('text and numbered buttons, links and fields'). That distinguishes it in practice from the mutating siblings (tumblr_click, tumblr_type) without naming them explicitly.

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 phrase 'the current page' implies a page must already be open, which is a soft prerequisite, but the description never says when to pick this over tumblr_status or when a read is unnecessary. Usage is implied rather than stated.

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