Skip to main content
Glama

maket_image

List, view, import, and delete image assets with controlled metadata updates. Viewing an image is required before writing metadata.

Instructions

When to use: manage the asset library (images). viewmeta is a required two-step: meta refuses any write without the context_token from the latest view call — proof the image was read before metadata is attributed.

Images live on disk under the assets dir; metadata lives in the store; both move together. list — list assets grouped by category; flags items missing metadata. view — load an asset inline (text + binary image) and return its context_token. MUST be called before meta. meta — write/update metadata; rejects without a current context_token. import — copy an asset in via url, path, or register-mode (filename-only for already-present files). Auto-optimises + thumbnails. delete — remove the file, thumbnail, and metadata row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFor import: HTTP(S) URL to download from.
pathNoFor import: local filesystem path to copy from.
tagsNoFor meta/import: searchable tags.
titleNoFor meta/import: human title.
actionYesOperation to run. See the tool description for the action table.
creditNoFor meta/import: attribution / photographer credit.
categoryNoFor list: filter to this category. For meta/import: category tag.
filenameNoAsset filename. Required for view/meta/delete. For import: destination filename (required in register-mode, derived from url/path otherwise).
overwriteNoFor import: overwrite an existing file with the same name.
descriptionNoFor meta/import: long prose.
orientationNoFor meta/import: orientation hint (landscape/portrait/square).
context_tokenNoFor meta (REQUIRED): token returned by the matching view call. Proves the image was read before its metadata is written.
Behavior5/5

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

Given no annotations, the description fully discloses behavioral traits: meta rejects writes without a current context_token; images live on disk under assets dir, metadata in store; import auto-optimizes and thumbnails; delete removes file, thumbnail, and metadata row.

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?

The description is efficiently structured: a concise introductory paragraph explaining the mandatory flow, followed by a bullet-list of actions with clear responsibilities. Every sentence adds value without redundancy.

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

Completeness5/5

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

With 12 parameters, no output schema, and multiple actions requiring orchestration, the description fully covers the tool's complexity. It explains the context_token dependency, action-specific parameter requirements, and lifecycle of assets, making it complete.

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 100% with detailed parameter descriptions. The tool description adds value by grouping parameters by action (e.g., context_token for meta, filename for view/meta/delete) and explaining the required view→meta flow, going beyond the schema alone.

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 explicitly states 'manage the asset library (images)' and enumerates five specific actions (list, view, meta, import, delete). It clearly distinguishes from sibling tools like maket_mermaid, maket_doc, etc., by focusing on image assets.

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 provides clear guidance on when to use each action and emphasizes the mandatory view→meta two-step flow. It does not explicitly mention when not to use this tool versus alternatives, but the context of image asset management is implicit.

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/ng-galien/maket'

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