Skip to main content
Glama

See the project's series

series_read
Read-only

The project's series: each with its kind (video, pictures or newsletter), where its episodes come from (a season Marsell plans, or the day's news on a topic), how often it comes out, whether it is running and the owner's standing yes, its narrator's voice, what comes next (for a news series: the newest day's story, or why there was none) and, for a video series, what it costs a month against the plan (every_scheduled_type: all its video types on the schedule together, when there is more than one; series_video_types_read gives each type's choices). Also the accounts the business has that a series can post to (known_accounts, for series_start). Marsell can run a series in the owner's own voice, made and posted every day from the day's news on a topic (for example daily archaeology news): each day it searches the news on the topic, drops what the series already reported, picks the best new story and makes a cited Short about it, narrated in a voice the project kept (the owner's own clone: voice_clone); a day with no new story gets no episode. Reading spends nothing.

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

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, read-only, closed-world operation. The description adds useful behavioral context such as 'Reading spends nothing' and explains how daily news series behave when no new story exists, though it does not discuss pagination or response shape beyond field descriptions.

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

Conciseness2/5

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

The description is a single dense run-on paragraph with many parentheticals and narrative examples. It is front-loaded with the core purpose, but it is substantially overlong and poorly structured for quick agent consumption.

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

Completeness5/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 carries the burden of explaining what is returned. It covers series attributes, accounts, video pricing, video type relationships, daily news series behavior, and voice usage, which is more than enough for an agent to call the tool and interpret its scope.

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?

There is only one parameter and schema coverage is 100%; the schema already explains that project accepts an id or exact name and is optional when the account has one project. The description adds no further parameter semantics beyond saying 'The project's series', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool reads a project's series, including their kinds, schedule, status, voice, next episode, video pricing, and posting accounts. It also distinguishes itself from series_video_types_read and references series_start, so an agent can identify its role among siblings.

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?

Usage is clear enough: read series data, use known_accounts for series_start, and use series_video_types_read for individual video type choices. It does not state exclusions or broader when-not-to-use conditions, but the alternatives mentioned are helpful.

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.