Skip to main content
Glama
Sign In
Scout

Scout

by Lautrek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_my_posts

Retrieve your recent posts from LinkedIn, X, or Medium with a configurable limit.

Instructions

Get your recent posts on a platform.

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": {
      "platform": "<platform>"
    },
    "name": "scout_my_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform: linkedin, x, medium
limitNoMax posts to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states 'get your recent posts' without mentioning authentication requirements, return format, pagination, or potential errors. This lack of detail leaves the agent uncertain about side effects or constraints.

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 description is a single sentence, which is concise, but it omits crucial information. While brevity is valued, here it compromises clarity and completeness, resulting in a moderate score.

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?

Given the tool's simplicity (2 parameters, no output schema), the description is incomplete. It fails to explain what 'recent' means, how the default limit works, or what response to expect. Without annotations, this leaves significant gaps for the AI agent.

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 coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond what the schema already provides (e.g., platform values, limit default). Thus, it meets the baseline but does not enhance understanding.

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 description states the verb 'Get' and resource 'your recent posts on a platform', clearly indicating its function. While it distinguishes from siblings like scout_post (create) and scout_search_posts (search), it does not explicitly clarify that it retrieves the authenticated user's own posts, which could be confused with a general search.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as authentication, or specific contexts where this tool is preferred over scout_search_posts.

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