Skip to main content
Glama
valentil

FeatureBoard MCP Server

by valentil

Save media asset

save_media

Persist generated assets (HTML, SVG, images) as UTF-8 text or base64 into a project's media folder with a .meta.json sidecar containing title, prompt, tags, and ticket.

Instructions

Save a generated asset into a project's media/ folder — a shareable HTML report (or SVG) as UTF-8 text, or an image as base64 (encoding:'base64'). You generate the content; this persists the bytes plus a .meta.json sidecar (title, prompt, tags, linked ticket, generatedAt) that list_media reads back. Name must be a plain filename with an extension, e.g. q3-report.html.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlain filename with extension, e.g. launch-report.html or chart.png.
tagsNo
groupNoVariation group id — save siblings under one group for side-by-side review (list_variations).
titleNoHuman title for the gallery.
promptNoThe prompt/goal this asset was generated from.
ticketNoBoard ticket this asset relates to, e.g. FBMCPF-39.
contentYesAsset contents: UTF-8 text, or base64 when encoding is 'base64'.
projectYes
encodingNoutf8
brandWordsNoBrand/trial words woven into this asset. If omitted, the project's configured brandWords are recorded automatically.
Behavior4/5

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

Annotations provide no safety hints, so the description carries the burden. It discloses sidecar creation (.meta.json), persistence behavior, and encoding options. No contradictions with annotations.

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?

Two efficient sentences with no waste. First sentence covers core purpose and formats; second clarifies a critical naming rule. Front-loaded and scannable.

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?

The description explains core functionality and sidecar generation but does not mention the return value or behavior on conflict (e.g., overwrite). For a 10-parameter tool with no output schema, this leaves some gaps.

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?

The schema covers 70% of parameters with descriptions, and the description adds useful context: naming convention ('plain filename with extension'), encoding usage, and that brandWords defaults to project settings if omitted. This adds meaning beyond the schema.

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 the verb 'Save' and the resource 'generated asset into a project's media/ folder', specifying file types (HTML, SVG, image) and encoding. It distinguishes from siblings like list_media and edit_media by focusing on creation and persistence.

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?

The description implies usage after generating content and notes that list_media reads the metadata sidecar. However, it does not explicitly state when not to use this tool or mention alternatives like edit_media or revert_media.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/valentil/featureboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server