agent-media

save_series_bible

Destructive

Save the season logline and beat map, one line per episode (usually Ep1–Ep10), plus the optional story bible and season grid. Omitted optional fields keep their saved value. leads: {a,b}: {want, wound, secret_id (a secrets id or null), hidden_asset, optional role, voice, arc, relationship_tension, visual_lock}. secrets: [{id, holder a|b, truth, planted_ep, half_reveal_ep, full_reveal_ep}]. grid: [{ep, goal, turn, cliffhanger_type partial_reveal|reversal_setup|intrusion|ticking_clock|betrayal_reveal, final_line, tension 1-10, payoff none|small|major}]. free_episodes: free episodes before login (default 3); the last free episode is the free-to-paid point. characters: {recurring id: {function, want, relation, arc?, voice?, comic_trait?}}; secrets holder and grid rows may use any character id, and grid rows take optional cast (ids), locations (indexes) and gag (sitcom). Returns season_check.warnings; fix the grid until it is clean.

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": {
      "series_id": "<series_id>",
      "logline": "<logline>",
      "beat_map": "<beat_map>"
    },
    "name": "save_series_bible"
  }
}

Input Schema

Name	Required	Description	Default
`grid`	No
`leads`	No
`tropes`	No
`logline`	Yes
`secrets`	No
`beat_map`	Yes
`series_id`	Yes
`characters`	No
`world_rules`	No
`core_promise`	No
`power_holder`	No
`power_ladder`	No
`free_episodes`	No
`emotional_engine`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / characters

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Characters"
+}

Changed10 schema fields changedOct 26, 2026

addedInput schema / properties / core_promise

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Core Promise"
+}

addedInput schema / properties / emotional_engine

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Emotional Engine"
+}

addedInput schema / properties / free_episodes

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Free Episodes"
+}

addedInput schema / properties / grid

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Grid"
+}

addedInput schema / properties / leads

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Leads"
+}

addedInput schema / properties / power_holder

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Power Holder"
+}

addedInput schema / properties / power_ladder

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Power Ladder"
+}

addedInput schema / properties / secrets

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Secrets"
+}

addedInput schema / properties / tropes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Tropes"
+}

addedInput schema / properties / world_rules

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "World Rules"
+}

AddedOct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description adds material context beyond them: 'Omitted optional fields keep their saved value' clarifies partial-update merge semantics, and 'Returns season_check.warnings' discloses a validation response despite no output schema. It still does not say what happens to fields that ARE supplied (replace vs merge) or what validation failures do to the write.

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?

Extremely dense but every clause carries load: purpose first, then nested field contracts, then partial-update semantics, then the return/validation loop. Bracket notation is terse but readable and no sentence is redundant.

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

Completeness3/5

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

For a 14-parameter, 0%-coverage, destructive, no-output-schema tool, the description covers the complex nested structures and the merge/validation behavior well, but the six story-bible scalar/list parameters are left effectively unspecified, so an agent cannot confidently populate them from the definition alone.

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?

With 0% schema description coverage the description carries the full burden, and it does document the highest-risk nested shapes in detail: leads fields (want, wound, secret_id, hidden_asset, visual_lock), secrets array, grid row fields with cliffhanger_type and payoff enums, characters map, and free_episodes semantics. However, six of the fourteen parameters (tropes, world_rules, core_promise, power_holder, power_ladder, emotional_engine) are only vaguely covered by the phrase 'optional story bible', leaving half the surface undocumented.

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 opening clause names a specific verb (save) and resource (season logline, beat map, story bible, season grid) and enumerates the payload shape, so an agent knows exactly what is persisted. It does not explicitly differentiate itself from near-siblings like save_story_state or save_episode_script, leaving the season-vs-episode boundary to be inferred.

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 rather than stated: the agent can infer this is the write path for season-level canon, and 'fix the grid until it is clean' gives a useful iterate-until-clean loop. There is no explicit when-to-use/when-not guidance and no routing to alternative tools such as save_story_state for episode-level state.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-media tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?