Skip to main content
Glama

List messages

list_messages
Read-only

Read Instagram and Facebook direct message history. Filter by platform or accountId to keep the response small. A message's story is set when it replies to one of the account's Instagram stories; pass that story.id as storyId to list every reply to the story, whose sender ids can be messaged with send_instagram_message.

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_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo
accountIdNo
profileIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "tiktok_ads",
      -  "facebook",
      -  "meta_ads",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "bluesky",
      -  "linkedin"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "tiktok_ads",
      +  "facebook",
      +  "meta_ads",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky",
      +  "linkedin",
      +  "linkedin_ads"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "tiktok_ads",
      -  "facebook",
      -  "meta_ads",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "bluesky"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "tiktok_ads",
      +  "facebook",
      +  "meta_ads",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky",
      +  "linkedin"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "facebook",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "bluesky"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "tiktok_ads",
      +  "facebook",
      +  "meta_ads",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "facebook",
      -  "whatsapp",
      -  "youtube",
      -  "x"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "facebook",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "facebook",
      -  "whatsapp",
      -  "youtube"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "facebook",
      +  "whatsapp",
      +  "youtube",
      +  "x"
      +]
  6. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context absent from annotations: filters shrink the payload, story replies are grouped, and senders can be followed up with send_instagram_message. However the storyId flow is not invocable, which undercuts the guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and filtering advice are front-loaded and tight. The third sentence is long and spends its weight on a storyId parameter that does not exist in the schema, so not every sentence earns its place.

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

Completeness2/5

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

With no output schema and zero parameter documentation, the description needed to explain all three parameters and the return shape. It covers two parameters loosely, omits profileId, and introduces a story flow the agent cannot execute, leaving the definition incomplete for its complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning. It explains platform and accountId only as filters, and never mentions profileId at all, leaving a third of the parameters unexplained while describing a nonexistent storyId.

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 first sentence gives a specific verb and resource ('Read ... direct message history') and names the platforms, which separates it from list_comments and list_posts. It is slightly misleading because the platform enum covers eleven networks while the description claims only Instagram and Facebook.

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 gives one concrete filtering tip ('Filter by platform or accountId to keep the response small') and sketches a story-reply workflow via send_instagram_message. It never states when to prefer this over list_comments or other list siblings, and the story workflow references a storyId parameter that the tool does not accept.

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