Skip to main content
Glama

Samuelz® Marketing

Fotos und Videos

list_social_images
Read-onlyIdempotent

Browse existing private image assets before choosing an image for a Maps draft or uploading an explicitly supplied original. Use list_business_profile_media for images already on Google instead. limit is 1–50 (default 20); cursor copies the returned nextCursor for this same library. List the current private image library and libraryRevision before upload. Requires current marketing:prepare and tenant Owner Marketing rights. Private previews require Owner login. No upload, provider access or publication.

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": "list_social_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum private library assets on this page, 1–50, default 20. This is not the list of images published on Google.
cursorNoExact nextCursor from the preceding private library page; omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Exact nextCursor from the preceding private library page; omit for the first page."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum private library assets on this page, 1–50, default 20. This is not the list of images published on Google."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further by naming the required scopes (marketing:prepare, tenant Owner Marketing rights), the Owner-login requirement for private previews, and the negative guarantee that no upload, provider access or publication occurs. It also notes libraryRevision is returned, which the agent needs before calling upload.

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?

Front-loaded with purpose and the alternative route, then parameters, then permissions. Slightly dense — the separate 'List the current private image library and libraryRevision before upload' sentence partly restates the opening sentence — but almost every clause carries unique information.

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?

For a two-parameter, read-only listing tool with no output schema, the description covers purpose, alternatives, pagination mechanics, permission prerequisites, and the absence of side effects. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds operative meaning: limit is 1–50 with default 20 and is not the count of Google-published images, and cursor must be copied from the returned nextCursor for this same library. That clarifies the copy-exact-cursor contract better than the schema does.

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 (browse/list) and resource (the current private image library), and explicitly separates it from two neighbors: list_business_profile_media for images already on Google and the upload path for supplied originals. An agent can route without opening any schema.

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?

Gives positive guidance (browse before choosing an image for a Maps draft, and list libraryRevision before upload) and a named alternative for the competing case (Google-hosted media). When-to-use and when-not-to-use are both explicit.

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