Skip to main content
Glama

Lumethic Photo Verification

by com.lumethic
OverviewDiscussionsAdmin

update_portfolio

Idempotent

Change the portfolio's display_name, tagline, website_url or slug, or publish/unpublish it with published=true/false. Pass an empty string to clear tagline or website_url; omit fields to leave them. The slug can change at most 3 times per 30 days. Unpublishing always works; other changes need a paid plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoNew public URL path; see create_portfolio for the rules.
taglineNoShort line under the name, max 160 characters. Empty string clears it.
publishedNotrue publishes the page, false takes it offline.
website_urlNoPhotographer's website, an https URL of max 200 characters. Empty string clears it.
display_nameNoNew name, 1-80 characters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / display_name / description
      Added value: +"New name, 1-80 characters."
    • addedInput schema / properties / published / description
      Added value: +"true publishes the page, false takes it offline."
    • addedInput schema / properties / slug / description
      Added value: +"New public URL path; see create_portfolio for the rules."
    • addedInput schema / properties / tagline / description
      Added value: +"Short line under the name, max 160 characters. Empty string clears it."
    • addedInput schema / properties / website_url / description
      Added value: +"Photographer's website, an https URL of max 200 characters. Empty string clears it."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description reveals important behavioral nuances: unpublishing always works, but other changes need a paid plan. This goes beyond the annotations to set user expectations about side effects and limitations.

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 compact and well-organized, presenting all key information in three sentences without redundancy or irrelevant details.

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?

Given the output schema exists and the tool is an update operation, the description covers the essential behavior, constraints, and edge cases (clearing, omitting, limits, paid plan). An agent has enough context to use it correctly without further lookup.

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 provides detailed descriptions for each parameter (e.g., slug rules, max lengths). The description adds clarifying context about clearing and omitting fields, but most parameter meaning is already captured in 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 action (change portfolio fields) and enumerates the specific fields and publish/unpublish behavior. It leaves no ambiguity about the tool's purpose.

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 explicitly explains how to clear fields (empty string), that omitted fields are left unchanged, and constraints on slug changes (max 3 per 30 days) plus the paid plan requirement. These are practical usage rules.

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

All Lumethic Photo Verification toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources