Skip to main content
Glama

tumblr_click

Clicks a numbered Tumblr page element to interact with posts, notes, or controls identified during the last read.

Instructions

Click a numbered element on the current Tumblr page.

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": {
      "element": "<element>"
    },
    "name": "tumblr_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it says nothing about what a click does beyond the act itself — whether it navigates, mutates state, waits for load, or what happens on error. "Current page" implies page-scoped behavior but does not confirm the last-read dependency or post-click conditions.

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 short sentence with the verb and scope front-loaded; nothing is wasted. It is arguably too terse for the risk of a click action, but it is not padded or buried.

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

Completeness3/5

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

The tool is simple (one required integer, no output schema, no annotations), so the description covers the core need. However, it omits the sequencing to tumblr_read, the effect of the click, and any failure modes, leaving meaningful gaps for an interactive browser action.

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 parameter is fully documented there, including its tie to the last read, so the baseline applies. The description's wording adds only that the number refers to the current page, a marginal restatement rather than new meaning.

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 ("click") and a specific target ("a numbered element on the current Tumblr page"), which is enough to distinguish it from siblings like tumblr_type (text entry) and tumblr_read (page extraction). It stops short of explicitly naming an alternative, but the action is unambiguous.

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?

Usage is only implied: "numbered element" plus the schema's "Element number from the last read" hints that a prior tumblr_read is required, but the description never states that prerequisite or when to prefer this over tumblr_type. An agent must infer the workflow.

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