Skip to main content
Glama

growthintel-mcp

Social Content Recommendations Tool

social-content-recommendations-tool
Read-onlyIdempotent

Returns AI-generated organic content strategy guidance for the authenticated tenant, based on REAL Meta platform engagement (reach, comments, shares, saves — synced daily, not inferred): which organic posts are lead-gen candidates vs. pure awareness/consideration content, and which high-scoring, not-yet-promoted organic posts are worth turning into paid ads. Needs enough recent posts to be meaningful; returns available=false with a reason when it can't.

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": "social-content-recommendations-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real value beyond them: the guidance is grounded in actual Meta engagement metrics synced daily rather than inferred, and the insufficient-data case returns available=false with a reason — a non-obvious behavioral trait worth disclosing.

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?

Purpose is front-loaded in the first clause, with supporting detail on data provenance and the failure mode following. The parenthetical metric list and em-dash construction make it dense, but every clause carries information the agent needs (what it returns, what it's based on, when it fails).

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 parameters and no output schema, the description carries the return-value burden and does so by naming the two categories of guidance and the available=false failure shape. It stops short of describing the response structure or how many posts constitute 'enough', but the essentials for correct invocation are present.

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?

The tool takes zero parameters, so there are no parameter semantics to explain and the baseline applies. The description correctly implies the tenant scope is derived from authentication rather than from an input argument, which preempts a natural 'where do I pass the account?' question.

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?

States a specific verb and resource — returns AI-generated organic content strategy guidance for the authenticated tenant — and enumerates the two judgement types it produces (lead-gen vs. awareness/consideration, and not-yet-promoted posts worth paid promotion). The word 'organic' implicitly separates it from creative-strategy-recommendations, but no sibling is named explicitly, so the 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 Guidelines3/5

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

Gives one precondition for use — 'needs enough recent posts to be meaningful' — and describes the failure path (available=false with a reason). There is no explicit statement of when to prefer this over the creative-strategy or campaign-performance siblings, so an agent must infer the boundary from the word 'organic'.

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