Skip to main content
Glama

Tumblr MCP Server and API by Cotlet

Follow blog in Tumblr

tumblr_follow_blog
Read-onlyIdempotent

Follow blog 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_follow_blog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 reinforces this with "opens nothing by itself," which prevents an agent from assuming the follow has been executed. It also discloses the return shape (screens, buttons, fields) despite there being no output schema. The Tumblr API/no-MCP-server aside adds background but no invocation-relevant behavior.

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 purpose and the browser-tool handoff are front-loaded, which is good. But the trailing sentence about Tumblr's public API v2, OAuth coverage and the absence of an official MCP server (with a checked-on date) is marketing/background that does not help an agent decide or invoke. "from ChatGPT, Claude or any AI agent" is also filler.

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?

With no output schema, the description correctly covers what is returned and what the agent should do next. The gap is the input side: a zero-parameter "follow blog" tool gives no statement of how the blog to follow is determined or what context the agent must have gathered first. For a tool this simple that is a moderate, not fatal, omission.

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 zero parameters, so the baseline is 4 and there is no schema meaning to supplement. However, the description never explains how the target blog is identified with no input fields at all — an agent must infer that the blog comes from conversation context. That is a missed opportunity but not a schema-documentation failure.

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 states a specific verb and resource ("Follow blog in the user's own Tumblr account") and immediately clarifies the surprising part: it returns step-by-step instructions rather than performing the follow. It distinguishes itself from the cotlet_browser_* siblings by naming them as the tools that actually execute the action. It stops short of naming any tumblr_* sibling it should be preferred over.

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?

It gives a clear two-step workflow: call this to get the in-Tumblr steps, then act with cotlet_browser_* inside the Tumblr Cloud Browser. That is real routing guidance rather than vague context. It does not state when this tool should be skipped or what to do if the user wants an API-based path instead.

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