Skip to main content
Glama

Tumblr MCP Server and API by Cotlet

Reblog post in Tumblr

tumblr_reblog_post
Read-onlyIdempotent

Reblog post in the user's own Tumblr account from ChatGPT, Claude or any AI agent. Returns how to do it in Tumblr step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Tumblr Cloud Browser. Tumblr's official API: Tumblr has a full public API v2 with OAuth for posts, queue, drafts, submissions, follows and notes, but no official MCP server (checked 17 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description usefully reinforces this with 'opens nothing by itself' and explains the return (screens, buttons, fields). The opening clause 'Reblog post in the user's own Tumblr account' implies an action the tool does not take, creating mild tension with the read-only annotation, and the nature of the returned guide is not elaborated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is front-loaded and clear, but the final sentence about Tumblr's official API and 'no official MCP server (checked 17 Oct 2026)' is tangential, dated, and does not help an agent select or invoke the tool.

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 zero-parameter guide tool with no output schema, it explains what it returns and what to do next, which is adequate. It leaves unexplained why a browser-based workaround is needed when sibling tumblr_* tools exist, which is the key ambiguity for an agent.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema 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?

The first sentence names a specific verb and resource (reblog a post on Tumblr), and the second clarifies that the tool returns a step-by-step guide rather than performing the action. It distinguishes itself from a bare action tool by stating it 'opens nothing by itself,' though it never distinguishes itself from tumblr_create_post or tumblr_edit_post.

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?

It does provide a clear next step: 'then do it with the cotlet_browser_* tools in the user's Tumblr Cloud Browser.' However, it gives no guidance on when to choose this guide tool versus the sibling tumblr_* tools, and no prerequisites or exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources