Skip to main content
Glama

Articles and content plan

get_content
Read-only

Articles Howseen writes for the brand and the brand's own pages. view: plan = content calendar, next article to write and to publish, stale facts; articles = drafts, scheduled and published articles; performance = indexing status, impressions and clicks per article; site_pages = the brand's own website pages. Read-only. Replies with metrics carry glossary: the dashboard's own explanation of each one.

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": "get_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly for view articles, performance. End date YYYY-MM-DD. Default: now.
fromNoOnly for view articles, performance. Start date YYYY-MM-DD. Default: all time.
viewNoWhat to return (default plan).
brandNoBrand id, name or domain (from get_account (view: brands)). Optional when the account has a single brand.
limitNoMax items to return (the default and the maximum depend on the view; a larger value is capped).
offsetNoItems to skip, for pagination.

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, so 'Read-only' adds nothing, but the description does disclose genuine behavioral detail beyond structured fields: that metrics replies carry a glossary explaining each metric, and what each view surfaces (stale facts, indexing status, next article to write/publish). It does not cover pagination behavior or what happens when limit exceeds the per-view cap.

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?

The view list is front-loaded and each clause maps one view to its contents, so every phrase earns its place. The single long semicolon-chain paragraph is dense but readable; splitting the view list into bullets would scan faster.

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?

With no required parameters, 100% schema coverage, and no output schema, the description supplies what matters most — the meaning of each view and the glossary behavior for metrics. The remaining gaps, per-view limits and pagination semantics, are partially delegated to the schema's limit/offset descriptions.

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?

Schema coverage is 100%, so the baseline is 3, and the description genuinely adds meaning beyond the schema's terse 'What to return' by explaining what each enum value yields (calendar, drafts/scheduled/published, indexing status and per-article impressions/clicks, own site pages). It says nothing extra about from/to, limit, offset, or brand, leaving those entirely to the schema.

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 names the resource (articles the brand writes plus its own pages) and enumerates all four views with concrete meaning, so an agent can tell what the tool returns. It does not explicitly contrast with siblings like manage_articles or publish_article, leaving the read-only split to be inferred from the 'Read-only' sentence.

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?

Usage is implied by the view enumeration — pick the view matching what you need — and the 'Read-only' line hints that mutations belong elsewhere. There is no explicit when-to-use versus manage_articles, get_traffic, or publish_article, and no statement of prerequisites or exclusions.

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.