Skip to main content
Glama

tumblr_open

Opens a Tumblr page in your signed-in Cloud Browser so you can manage blog posts, queues, drafts, and asks.

Instructions

Open a Tumblr page in your signed-in Cloud Browser (default https://tumblr.com) to work with manage blog posts, queues, drafts and asks.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://tumblr.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that the browser is 'signed-in' (auth is handled) and that there is a default landing URL. It does not say whether opening replaces the current page or tab, what happens on session expiry, or whether any rate limiting applies for a stateful browser tool.

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?

A single front-loaded sentence with the action and default stated up front. The closing purpose clause is awkwardly worded and could be trimmed, but there is no filler or repetition.

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?

For a one-parameter navigation tool with no output schema this covers the essentials, but an agent is left not knowing what comes back after opening (page content, handle, readiness state) or what the natural next step is among tumblr_read/tumblr_click. Given the tool opens a stateful browser session, a sentence on post-open state would complete it.

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?

Only one optional parameter at 100% schema coverage, so the schema already documents the url and its default. The description restates the default, which is redundant but harmless; no additional syntax or format detail is needed for a plain URL.

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?

Names a specific verb (open) and resource (a Tumblr page in the signed-in Cloud Browser) and states the default URL, which is enough to tell it apart from tumblr_click/tumblr_read/tumblr_type. The trailing clause 'to work with manage blog posts, queues, drafts and asks' is grammatically garbled and muddies rather than sharpens the stated scope.

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?

Implies this is the entry point for starting a session before interacting with posts, queues, drafts or asks, but never states when to use this versus tumblr_read or tumblr_status, nor any precondition such as an existing session or an already-open page. Usage is inferable but not spelled out.

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