Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

List Discovered Posts

list_discovered_posts
Read-onlyIdempotent

Retrieve read-only posts published outside AdaptlyPost across connected accounts within a date range to review external activity or fill a content calendar.

Instructions

Posts found on the connected accounts that were not published through AdaptlyPost (published natively or with another tool), inside the window: text, thumbnail, permalink, account and publish time. They are read-only; their metrics are in list_post_analytics. Use it to show what an account posted outside AdaptlyPost or to fill in the calendar. Needs the analytics.read permission.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_discovered_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the reporting window (ISO 8601). Must not be earlier than from
fromYesStart of the reporting window as an ISO 8601 date or instant (e.g. "2026-08-01"). Metrics cover posts published between from and to; the comparison window is the same length immediately before from
limitNoPosts to return (default 200)
platformsNoRestrict to these platforms; omit for every platform with analytics. MASTODON, TELEGRAM, TUMBLR and WORDPRESS have no analytics and are ignored. GOOGLE_BUSINESS reports location impressions only, with no per-post numbers
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another
connectionIdsNoRestrict to these accounts, by the account id from list_accounts; omit for every account

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with posts: one { id, platform, publishedAt, text, thumbnailUrl, permalink, connectionId, accountName } per post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds real context: the required analytics.read permission and the fact that per-post metrics live in a different tool. It doesn't discuss ordering or response volume, but with an output schema present that is acceptable.

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 sentences, front-loaded with the definition, then the read-only/metrics pointer, then usage and permission. The first sentence is a long chain of qualifiers but every clause carries information; nothing is padded.

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 read-only listing tool with a full input schema and an output schema, the description covers identity, exclusion scope, where metrics live, and the auth prerequisite. Only minor gaps remain (ordering/pagination behavior, explicit contrast with list_posts).

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 description coverage is 100%, including rich notes on platform support, workspace scoping and the from/to window, so the schema carries the parameter burden. The description mentions the window only implicitly via 'inside the window' and adds no meaning for limit, platforms, connectionIds or workspaceId, so the baseline of 3 is appropriate.

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 and resource ('posts found on the connected accounts that were not published through AdaptlyPost') and enumerates returned fields (text, thumbnail, permalink, account, publish time). The 'not published through AdaptlyPost' scoping is exactly what distinguishes it from the sibling list_posts, so an agent can choose without opening either schema.

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?

Gives two concrete use cases ('show what an account posted outside AdaptlyPost or to fill in the calendar') and explicitly redirects metrics work to list_post_analytics. It lacks an explicit 'do not use this for posts you published — use list_posts' exclusion, so the boundary is implied by the negative scoping rather than stated as routing guidance.

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

Deploy Server

Other Tools