Skip to main content
Glama

write_upload_asset

Attach a file to a page using base64 data and return the Markdown link needed to embed it. Use this to add uploads when local file paths cannot be read.

Instructions

Attach a file to a page from base64 data; answers with the Markdown link to embed it.

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": {
      "page": "<page>",
      "filename": "<filename>",
      "base64": "<base64>"
    },
    "name": "write_upload_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
base64YesFile content as base64; local paths are not read
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotated behavior — that the call returns a Markdown link — but says nothing about persistence semantics, what happens if a file with the same filename already exists, size limits, or permissions.

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?

One tight sentence with the action front-loaded and the return value in the same breath; no filler, no repetition of the tool name.

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?

Since there is no output schema, the description's mention of the returned Markdown link is important and correct. However, for a write/mutation tool with three required parameters it omits duplicate-filename behavior, content-size limits, and whether the upload is idempotent, leaving real gaps for an agent to guess at.

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?

Schema coverage is 67% and the only undocumented parameter is 'filename', but the description reinforces the key semantic constraint that content comes as base64 data rather than a path (the schema makes that explicit too). It adds only modest meaning beyond the schema, but the schema carries most of the load.

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?

States a concrete verb and resource ('Attach a file to a page'), names the input form ('from base64 data') and the result ('Markdown link'), which is enough to separate it from siblings like write_rename_asset or read_assets. It does not explicitly disambiguate against those siblings, so it stops short of a 5.

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 only implied: the 'base64 data' and 'link to embed it' clauses suggest the caller has inline file bytes and wants embeddable markup. There is no explicit when-to-use/when-not guidance and no naming of alternatives such as read_assets for retrieving existing files.

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