Skip to main content
Glama

company list posts

company_list_posts
Read-onlyIdempotent

Read posts in ONE Agency Workspace, optionally filtered by publishing status, approvalStatus or channelKey. includeApproval opts in to approval fields. Follow nextCursor with unchanged filters; cursor is scoped to caller and workspace.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "company_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoOpaque nextCursor from the previous page; keep every other filter unchanged
statusesNo
channelKeyNoExact channel key from company_list_channels, not the connection database ID
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
approvalStatusNoFilter by the current client approval state, independently of publishing status
includeApprovalNoOpt in to client approval fields; omitted by default for compatibility

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / approvalStatus / enum
      Previous value: -[
      -  "none",
      -  "pending",
      -  "approved",
      -  "changes_requested",
      -  "outdated"
      -]New value: +[
      +  "none",
      +  "pending",
      +  "approved",
      +  "declined",
      +  "changes_requested",
      +  "outdated"
      +]
  2. Added

TDQS

A4/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), and the description adds genuinely new behavior: cursor is scoped to caller and workspace, filters must stay unchanged while paging, and includeApproval is an opt-in that exists purely for backward compatibility. That last point explains a non-obvious default that the agent would otherwise misread as an omission.

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?

Three tight sentences, no filler, with the scope constraint front-loaded and pagination guidance last where it belongs. Every clause carries actionable information.

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?

With no output schema and seven parameters, the description covers scope, filtering, and pagination well, and the includeApproval note signals that approval fields are otherwise absent from results. It is slightly thin on what a returned post record actually contains, which matters since no output schema exists to fill that gap.

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?

At 71% schema coverage, the schema already documents cursor, channelKey, workspaceId, approvalStatus and includeApproval with meaningful descriptions the tool text largely restates. The one added nuance is that approvalStatus is filtered independently of publishing status, but the schema already states that verbatim. Marginal value beyond structured fields.

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?

"Read posts in ONE Agency Workspace" gives a specific verb plus resource and constrains scope to a single workspace, and the optional filter axes (publishing status, approvalStatus, channelKey) sharpen what is being read. It does not explicitly name the sibling it is not (list_posts for personal scope, company_list_linkedin_page_posts), so differentiation is inferred rather than stated.

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?

The workspace-scoped framing plus the "follow nextCursor with unchanged filters" instruction gives clear operational context for when and how to call it, and the filter sentence shows the available narrowing options. It stops short of explicit exclusions such as "use list_posts for personal accounts" or "use company_get_post for a single post by ID."

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.