Skip to main content
Glama

Get Posts

get_posts
Read-onlyIdempotent

[Read · free] List a tracked profile's persisted posts with full metrics and text — query against the local post library, no LinkedIn pull, free. Use this when the caller already has a profile_id and wants to read its posts. Filter by date range, post type, minimum engagement, or text. Pass scope (a post_collections.id) to restrict to a specific collection (e.g. an external profile, topic stream, or hand-curated set). Paginated. For keyword/semantic search across posts, use search_posts. For fresh LinkedIn pulls, use linkedin_profile_posts.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "get_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based)
scopeNoOptional post_collections.id to filter posts to a specific collection
searchNoText search across post content (case-insensitive)
date_toNoEnd date (ISO 8601)
sort_byNoSort fieldpublished_at
sort_dirNoSort directiondesc
date_fromNoStart date (ISO 8601, e.g. 2025-01-01)
page_sizeNoResults per page (max 50)
post_typeNoFilter by post type
profile_idYesTracked profile ID from list_profiles
min_engagementNoMinimum total engagement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, yet the description still adds real context: reads from a local persisted library rather than hitting LinkedIn, costs nothing, and is paginated. It does not state page-size limits or empty-result behavior beyond what the schema already says, which keeps it from a 5.

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?

Front-loaded with a cost/access tag and the core action, then preconditions, filters, scope, pagination, and alternatives in a logical order. Slightly dense and mildly repetitive on the LinkedIn-pull point, but no sentence is filler.

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 an 11-parameter, paginated read tool with no output schema, the description covers the data source, filter surface, pagination, and return content ("full metrics and text"). It stops short of describing what the metrics include or how paging terminates, but nothing needed to invoke it correctly is missing.

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?

Schema description coverage is 100%, so baseline is 3; the description earns above that by explaining the intent behind `scope` as a post_collections.id for external profiles, topic streams, or hand-curated sets, and by grouping the filter axes (date range, post type, minimum engagement, text). It adds conceptual meaning rather than restating field names.

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?

Names a specific verb and resource ("List a tracked profile's persisted posts") and immediately bounds the source of data ("query against the local post library, no LinkedIn pull"). It also explicitly distinguishes itself from search_posts and linkedin_profile_posts, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

States the exact precondition ("when the caller already has a profile_id and wants to read its posts") and gives two named alternatives with the condition that selects each: search_posts for keyword/semantic search, linkedin_profile_posts for fresh pulls. When-to-use and when-not-to-use are both present.

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