Skip to main content
Glama

Vifo

by app.vifo
OverviewDiscussionsAdmin

Show items to the traveller

show_media
Idempotent

Show the traveller a set of their own photos and videos: a short-lived link, no sign-in needed. Use it when you want them to look before you decide — 'are these three from the Kyoto trip?', 'here is what is still unfiled', 'day 3 in the order I have it', or the results of a search. Pick the scope with exactly one of three: media_ids (the ones search or list_media returned, in the order you want them shown), trip_id (everything in that trip, narrowable with from/to), or unfiled: true (everything not filed into a trip yet — use this rather than listing the unclaimed pool and passing its ids back). Each item carries a number so they can answer 'the 2nd and 5th'. Not a share link: this is for the owner, read-only, expires in 24 hours (1–72), and shows raw material rather than the finished trip. Calling again with the same selection returns the same link while it is live, with the new note on it — so ask your next question by calling again, not by sending the old address with a new question in the chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoYYYY-MM-DD, inclusive. Only with trip_id.
fromNoYYYY-MM-DD, inclusive, local to the photo. Only with trip_id.
noteNoShown at the top of the page — the question you want answered. (at most 500 characters)
trip_idNoEverything in this trip; narrow with from/to. A live view: the page re-reads the trip every time it is opened, so material added later shows up and material moved out or deleted disappears. (must not be empty)
unfiledNoPass true for everything not filed into a trip yet. Only true is a selection — there is no unfiled: false; to show something else, leave this out and give media_ids or trip_id. A live view: the page re-reads the pool every time it is opened, so anything filed into a trip in the meantime drops off it.
media_idsNoSpecific items, in the order to show them. (at least 1 item, at most 200 items)
ttl_hoursNoDefault 24. (≥1, ≤72)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses key behaviors beyond annotations: link expiry (24 hours, 1–72), no sign-in needed, live-view behavior for trip_id and unfiled, item numbering, and idempotent regeneration with the same link and updated note. This complements the idempotentHint annotation and clarifies the read-only nature of the resulting page.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but dense and front-loaded with the core purpose. It uses examples and clear scope rules; some sentences could be tightened, but each contributes either usage guidance, behavioral context, or a distinction from alternatives.

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?

Despite having no output schema, the description conveys what the agent gets back: a short-lived link, the same link on repeat calls, item numbering for reference, and the note display. It also addresses authentication, expiry, and live-view behavior, making it sufficiently complete for correct invocation.

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 already covers all parameters at 100%, but the description adds selection semantics: exactly one of media_ids, trip_id, or unfiled:true, ordering for media_ids, and why unfiled:true is preferable to passing a pool of ids. This goes beyond the schema's per-parameter descriptions without duplicating them.

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 states a specific verb and resource: 'Show the traveller a set of their own photos and videos: a short-lived link, no sign-in needed.' It clearly distinguishes itself from share links and other siblings by emphasizing this is for the owner, read-only, and temporary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('Use it when you want them to look before you decide') with concrete examples, and provides exclusions: 'Not a share link' and 'use unfiled rather than listing the unclaimed pool and passing its ids back.' It also names related tools like search and list_media, making the choice of scope clear.

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

All Vifo toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources