get_mod_mediaRetrieve a mod's author images and videos as shown in the mod editor. Requires an author or editor session.
List a mod's author images (id, url, title, primary/thumbnail) and videos as the mod editor shows them. Author/editor session required.
| Name | Required | Description | Default |
|---|---|---|---|
| game | Yes | Game domain name, e.g. "skyrimspecialedition" | |
| mod_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, open-world, and idempotent behavior. The description adds meaningful context by specifying the auth/session requirement and the editor-specific presentation of the media list, which is beyond what the annotations or schema communicate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence packs the action, the resource, the included fields, the view context, and the auth requirement with no filler. The most important scoping information ('author images and videos') is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple read-only list operation with two straightforward parameters and no output schema. The description conveys the returned media fields, the editor context, and the required session, so an agent has enough to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50%: game has an example, but mod_id has no description. The tool description does not explain either parameter further, relying largely on the tool name and schema types. This is acceptable but not a strong compensation for the undocumented mod_id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('a mod's author images and videos'), and clarifies the editor-facing view with 'as the mod editor shows them.' This clearly distinguishes it from sibling tools that upload or delete media, and from get_mod which returns broader mod data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states the required session context ('Author/editor session required'), which tells an agent when it can be used. It does not explicitly name alternatives or give a 'when not to use this' condition, but the editor-scoped phrasing makes the intended use clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.