Skip to main content
Glama

Get content memory

mynahcast_get_content_memory
Read-onlyIdempotent

List what the brand already drafted, published or had rejected (hooks, topics, claims, rejection reasons). Read before drafting: avoid repeating recent hooks, topics and claims, and learn from rejectionReason. Newest first. Filter by status, platform, channelId, styleId, since or text.

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": {
      "brandId": "<brandId>"
    },
    "name": "mynahcast_get_content_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
limitNo
sinceNo
statusNo
brandIdYes
styleIdNo
platformNo
channelIdNo

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "bluesky",
      -  "mastodon",
      -  "telegram",
      -  "discord",
      -  "x",
      -  "linkedin",
      -  "youtube",
      -  "tumblr",
      -  "nostr",
      -  "lemmy",
      -  "misskey",
      -  "slack",
      -  "matrix",
      -  "devto",
      -  "hashnode",
      -  "wordpress",
      -  "listmonk"
      -]New value: +[
      +  "bluesky",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "x",
      +  "linkedin",
      +  "youtube",
      +  "tumblr",
      +  "nostr",
      +  "lemmy",
      +  "misskey",
      +  "slack",
      +  "matrix",
      +  "devto",
      +  "hashnode",
      +  "wordpress",
      +  "listmonk",
      +  "instagram",
      +  "threads",
      +  "facebook"
      +]
    • changedOutput schema / properties / items / items / properties / platform / enum
      Previous value: -[
      -  "bluesky",
      -  "mastodon",
      -  "telegram",
      -  "discord",
      -  "x",
      -  "linkedin",
      -  "youtube",
      -  "tumblr",
      -  "nostr",
      -  "lemmy",
      -  "misskey",
      -  "slack",
      -  "matrix",
      -  "devto",
      -  "hashnode",
      -  "wordpress",
      -  "listmonk"
      -]New value: +[
      +  "bluesky",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "x",
      +  "linkedin",
      +  "youtube",
      +  "tumblr",
      +  "nostr",
      +  "lemmy",
      +  "misskey",
      +  "slack",
      +  "matrix",
      +  "devto",
      +  "hashnode",
      +  "wordpress",
      +  "listmonk",
      +  "instagram",
      +  "threads",
      +  "facebook"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds non-schema behavior: results are ordered 'Newest first', which is essential for the stated deduplication use case. It omits result volume/pagination behavior, so a 5 is not warranted.

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?

Three tight sentences with no filler: what it lists, why to call it, then the shape of results and filters. The deduplication rationale is front-loaded right after the purpose statement.

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 an output schema present, return values need no explanation, and the description covers ordering, purpose, and filter surface for an 8-parameter read tool. The remaining gap is the limit parameter and result-volume expectations, which an agent calling this repeatedly for deduplication would want to know.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only partly does. 'Filter by status, platform, channelId, styleId, since or text' names the filters but adds no semantics — for example what field 'text' matches, whether 'since' is a lower or upper date bound, or that limit caps at 200.

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 ('List what the brand already drafted, published or had rejected') and enumerates the content types returned (hooks, topics, claims, rejection reasons). This separates it from generic listing siblings like mynahcast_list_posts by making clear it is the brand's institutional memory of prior content.

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?

Gives explicit timing guidance — 'Read before drafting' — plus the two concrete reasons to call it (avoid repeating hooks/topics/claims, learn from rejectionReason). It does not name a when-not condition or an alternative tool, which keeps it short of a 5.

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