Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get posting overview

get_posting_overview
Read-onlyIdempotent

Check an account's connected LinkedIn and X profiles, timezone, weekly posting cadence, scheduled, draft and failed post counts, plus next open slots in one read-only view.

Instructions

Where this account can post (connected LinkedIn and X accounts), its timezone and posts per week, how many posts are scheduled, in drafts or failed, and the next open slots. Reads only.

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": "get_posting_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered and 'Reads only' mostly restates it. The description does add value by disclosing what data is surfaced (destinations, timezone, cadence, queue-state counts, open slots), though it says nothing about formatting, limits, or whether counts are scoped to the selected account.

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?

A single front-loaded sentence that leads with the primary content ('Where this account can post') and appends the remaining fields efficiently. The closing 'Reads only' is slightly redundant against the annotations but costs little.

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, the description appropriately enumerates the returned content, which is the key thing an agent needs. Combined with rich read-only annotations and a single optional, schema-documented parameter, the definition is complete enough for correct invocation, though it could note that the overview is account-scoped.

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?

The description never mentions account_id, so it adds no meaning beyond the schema. However, the schema itself carries a clear inline description of account_id (only needed for teammates in multiple accounts), so the parameter is not left undocumented — baseline 3 applies.

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 names a specific resource bundle — connected LinkedIn/X accounts, timezone, posts per week, scheduled/draft/failed counts, and next open slots — so an agent knows this is a read-only posting status summary. It does not explicitly distinguish itself from siblings like get_post or get_campaign_results, but the enumerated contents make the scope reasonably unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. 'Reads only' signals the absence of side effects but is not usage guidance for choosing this tool over get_post or the campaign/results tools.

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