Skip to main content
Glama

Discover Brand Images

discover_brand_images
Read-onlyIdempotent

Collect candidate brand images from the user's website, Instagram posts and earlier research (up to 24). Show them to the user to pick from, then save the selection with select_brand_images.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_brand_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
instagramHandleNoInstagram handle to pull post images from; defaults to the user's saved profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds real value beyond them: a cap of 'up to 24' results, that it is an interactive show-to-user step, and that a separate save tool completes the flow.

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 tightly packed sentences with zero filler, front-loading the collection action and cap before the follow-up save step. Every clause earns its place.

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

Completeness4/5

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

For a single-optional-param discovery tool with no output schema and annotations already covering safety, the description covers sources, cap, and the next step well. It could say more about behavior when no candidates are found or how the selection step is triggered, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 1 parameter at 100% schema description coverage, the schema already documents instagramHandle fully, including its default. The description only obliquely references Instagram as a source, adding no syntax or override detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Collect candidate brand images') plus the three sources (website, Instagram posts, earlier research), so the agent immediately understands the resource and scope. It is clearly distinguishable from siblings like search_my_images (search a library) and recommend_images_for_post (recommend for a single post).

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 embeds the workflow context: collect candidates, show them to the user, then save via select_brand_images, explicitly naming the follow-up tool. It gives clear when-to-use context but does not explicitly contrast with alternatives such as search_my_images or recommend_images_for_post.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources