Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

getMultiImagePost

Read-onlyIdempotent

Fetch a multi-image post (album) by its group ID. Returns a lean record with photo count and cover URL; use optional flags to include full content, author, photos, or extras.

Instructions

Get a single album group - Fetch a single portfoliogroup record. Read-only.

Lean-by-default keep-list: same shape as listMultiImagePosts — core identity + routing fields plus total_clicks (only when > 0), total_photos, cover_photo_url, cover_thumbnail_url. Restore via flags: include_content=1 (full group_desc HTML), include_author_full=1 (full user nested — default omits author detail; call getUser(user_id) otherwise), include_clicks=1, include_photos=1 (full users_portfolio photo array), include_extras=1 (everything else — geo, post dates, timestamps, tokens, etc.).

Use when: fetching one multi-image post by group_id. Photos in this post are loaded separately via listMultiImagePostPhotos with group_id filter.

Required: group_id.

See also: listMultiImagePosts (enumerate many; supports keyword filter via property + property_operator=LIKE).

Returns: { status: "success", message: [{...record}] } - the message array contains 1 lean-shaped record when found. Empty or HTTP 404 when not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYes
include_contentNoOpt in to return the full `post_content` HTML body. Default stripped (`post_title` + `post_caption` always returned).
include_author_fullNoOpt in to return the full original `user` nested object (every field BD returns, including `password` hash, session `token`, `cookie`). Default: author detail omitted entirely — call `getUser(user_id)` when needed.
include_clicksNoOpt in to return `user_clicks_schema.clicks` array. Default: `total_clicks` count surfaced only when > 0; absent means zero clicks.
include_photosNoOpt in to return `photos_schema` array. Default: `total_photos` count only (`image_main_file` URL always returned).
include_extrasNoOpt in to return ALL remaining fields on this resource that are not in the lean-by-default keep-list and not gated by another `include_*` flag. Lean default returns only the core identity, routing, and load-bearing fields. `include_extras=1` restores everything else (geo, all hero_*, layout/sidebar/menu config, all display toggles, admin metadata, etc.). Resource-specific — see each tool's description for what the extras bundle contains.
Behavior5/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint. Description adds details: lean-by-default keep-list, flags to restore more data, return format (status, message array), and behavior on not found (empty or HTTP 404). No contradiction with annotations.

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?

Well-structured with sections. Front-loaded purpose, then keep-list, use cases, and return format. Every sentence adds value without redundancy.

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 no output schema, the description fully explains the return shape, lean default behavior, and how to control output via flags. Provides guidance on related tools for photos. Sufficient for agent to correctly invoke.

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?

Input schema covers 83% of parameters with descriptions. Description adds value by explaining the lean keep-list and the purpose of each include flag, especially the extras bundle. It also reiterates group_id is required.

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?

Clearly states it fetches a single album group/portfoliogroup record. Distinguishes from sibling tools like listMultiImagePosts (enumerate many) and listMultiImagePostPhotos (load photos separately).

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?

Explicitly states to use when fetching one multi-image post by group_id and that photos are loaded via listMultiImagePostPhotos. Provides a 'See also' link to listMultiImagePosts. Does not explicitly list when not to use, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brilliantdirectories/brilliant-directories-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server