Skip to main content
Glama

add_blog

Create and publish new blog posts to the MCP Blog API by providing title and content.

Instructions

Add a new blog to the mock API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
bodyYes

Implementation Reference

  • main.py:28-32 (handler)
    The add_blog tool handler function, decorated with @mcp.tool(), which sends a POST request to add a new blog post with title and body to the mock API.
    @mcp.tool()
    def add_blog(title: str, body: str):
        """Add a new blog to the mock API."""
        response = httpx.post(mock_api_url, json={'title': title, 'body': body})
        return response.json()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Add a new blog' which implies a write/mutation operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, idempotency, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, stating the core purpose without unnecessary elaboration.

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?

Given a mutation tool with no annotations, 0% schema coverage, no output schema, and 2 required parameters, the description is incomplete. It lacks parameter explanations, behavioral context, and usage guidelines, making it insufficient for effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description doesn't mention parameters at all, failing to add any meaning beyond the input schema. For a tool with 2 required parameters, this leaves semantics completely undocumented.

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 clearly states the action ('Add a new blog') and target resource ('to the mock API'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_blogs' or 'search_blogs', which would require mentioning this is for creation versus retrieval/search operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for creation, or compare to sibling tools like 'get_blogs' or 'search_blogs', leaving the agent without explicit usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tussanakorn/POC_MCP_Protocol_using_FastMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server