Skip to main content
Glama

Choose the logo a carousel shows

flypost_carousel_logo

Which logo this carousel's slides show (the deck editor's logo picker), e.g. the white version on a dark template. Position and size come from the template and the brand's carousel settings. 'default' uses the project's default logo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content_bank_item_id": "<content_bank_item_id>",
      "logo_id": "<logo_id>"
    },
    "name": "flypost_carousel_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
logo_idYesFrom flypost_list_logos.
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-destructive mutation, so the description's main added value is that it changes only the displayed logo while position and size remain template/brand-driven, and that 'default' selects the project default. It does not describe replacement semantics, validation, or success behavior beyond that.

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?

Three short sentences, front-loaded with the selection purpose and followed by the layout caveat and default behavior. The parenthetical editor reference is slightly extraneous but not wasteful.

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

Completeness3/5

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

For a two-parameter mutation with no output schema, the description covers the selection behavior, default value, and layout boundary reasonably well. It is still incomplete because one required parameter (content_bank_item_id) is unexplained and the result of a successful call is not stated.

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?

Schema coverage is 50%; the logo_id field is partly documented in the schema, and the description usefully adds that 'default' is a valid logical value even though no enum is declared. However, content_bank_item_id has no schema description and the description never explains that it identifies the carousel.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states this tool selects which logo a carousel's slides display, and clarifies that position and size are handled by the template and brand settings rather than this call. That distinguishes it from placement-oriented siblings such as flypost_place_logo, though it does not explicitly name that sibling.

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

Usage Guidelines3/5

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

It implies use when changing the logo in the deck editor and notes 'default' as a value, but gives no explicit when-to-use guidance or exclusions relative to flypost_place_logo, flypost_upload_logo, or template switching. The agent must infer the boundary from the layout caveat.

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.