Skip to main content
Glama

get_weekly_digest

Read-only

Klyf Pro. The creator's week in review for their own YouTube channel: what changed this week versus last (views and subscribers), the video that stood out, the one thing to fix, and a comment worth answering, ending with one action for the week. Call this when the user asks for their weekly digest or summary, what changed or happened this week, how their week went, their week in review, or to catch them up on the channel. For a point-in-time overview use audit_channel; for direction over months use check_growth. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

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_weekly_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it takes no input, reads the real connected channel directly, and instructs the agent not to ask the creator for context, links, or titles before calling. It does not say what happens if no channel is connected or if the user is not on the Pro tier, which is the only remaining gap.

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 lead clause identifies the resource and the substance of the response up front, followed by triggers and then alternatives — a sensible front-loaded order. The opening "Klyf Pro." is terse but arguably earns its place as a tier gate, though the multi-clause second sentence is dense and could be split.

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?

There is no output schema, so the description carries the burden of describing return content, and it does so by naming each section of the digest. For a zero-argument read tool that is nearly complete; only failure modes (no connected channel, non-Pro account) go unmentioned.

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?

Zero parameters, so the baseline is 4. The description reinforces this by stating "Needs no input" and warning against soliciting context first, which prevents an agent from fabricating unnecessary arguments or stalling on a clarification turn.

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?

States a specific verb and resource ("The creator's week in review for their own YouTube channel") and then enumerates exactly what the digest contains: week-over-week views and subscriber deltas, a standout video, one thing to fix, a comment worth answering, and a closing action. This is far more specific than the name alone and lets an agent predict the response shape.

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

Usage Guidelines5/5

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

Lists concrete trigger phrasings ("weekly digest or summary, what changed or happened this week, how their week went, their week in review, or to catch them up") and explicitly routes alternatives: audit_channel for a point-in-time overview, check_growth for multi-month direction. Both when-to-use and when-not-to-use are covered with named siblings.

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