Skip to main content
Glama

Outil.io

Create blog page

create_blog_page

PAGE D’INDEX D’UN BLOG À MODIFIER : chaque blog actif a déjà une page d’index publiée automatiquement (titre, description, liste dynamique de ses articles, en-tête et pied de page de l’accueil), à /p//. Cet outil la crée comme vraie page du site (type blog), publiée à la même adresse, pour la modifier comme une page (get_page_structure / apply_page_changes). Renvoie la page existante si elle est déjà créée.

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": {
      "blogId": "<blogId>"
    },
    "name": "create_blog_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
blogIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly=false, destructive=false and openWorld=false, so the safety profile is known. The description adds meaningful behavior the annotations cannot: the page is published at the same existing address, inherits home page header/footer, and the call is effectively idempotent because it returns the existing page if it already exists. It does not say what happens to prior manual edits or how long publishing takes, which keeps this at a 3.

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?

Dense and front-loaded: the key constraint (the index page already exists automatically) comes first, then what the tool produces, then the follow-up tools. Two sentences carry a lot without filler, though the capitalization-heavy preamble and the parenthetical tool list make it slightly harder to scan.

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

Completeness4/5

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

For a single-parameter mutation with no output schema, the description covers what gets created, where it is published, and the return value semantics (existing page if already created). It is close to complete; the main omissions are the shape of the returned page and whether the page inherits or copies the blog's dynamic article list.

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?

Only one parameter (blogId) with 0% schema description coverage, so the description must carry the meaning. It implies the id identifies the blog whose auto-generated index page is at /p/<project>/<slug> parameter. However, it never says whether blogId is the numeric blog id versus the slug or project id, leaving ambiguity that matters given exclusiveMinimum:0 on the integer.

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 and resource: it creates the blog's auto-generated index page as a real site page of type 'blog' at the same URL. The scope is precise enough to separate it from a generic page creation, but the opening header ('PAGE D'INDEX D'UN BLOG À MODIFIER') reads like a target description rather than an action, and no other create_* sibling is named for contrast.

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?

Clearly frames the situation: each active blog already publishes an index page automatically, and this tool converts it into an editable page so it can be modified via get_page_structure / apply_page_changes. That is strong when-to-use guidance with named follow-ups. It never states the inverse case (e.g., when to use create_page or create_article_page 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.