Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_linkedin_posts

Retrieve LinkedIn posts from your Metricool brand account by specifying a date range and blog ID to analyze and manage social media content effectively.

Instructions

Get the list of Linkedin Posts from your Metricool brand account.

Args: init date: Init date of the period to get the data. The format is YYYY-MM-DD end date: End date of the period to get the data. The format is YYYY-MM-DD blog id: Blog id of the Metricool brand account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blog_idYes
end_dateYes
init_dateYes

Implementation Reference

  • Handler function for the 'get_linkedin_posts' tool. It is registered via the @mcp.tool() decorator. Fetches LinkedIn posts data from the Metricool API using a GET request, with parameters for date range and blog ID.
    async def get_linkedin_posts(init_date: str, end_date: str, blog_id: int) -> str | dict[str, Any]:
        """
        Get the list of Linkedin Posts from your Metricool brand account.
    
        Args:
         init date: Init date of the period to get the data. The format is YYYY-MM-DD
         end date: End date of the period to get the data. The format is YYYY-MM-DD
         blog id: Blog id of the Metricool brand account.
        """
    
        url = f"{METRICOOL_BASE_URL}/v2/analytics/posts/linkedin?from={init_date}T00%3A00%3A00&to={end_date}T23%3A59%3A59&blogId={blog_id}&userId={METRICOOL_USER_ID}&integrationSource=MCP"
    
        response = await make_get_request(url)
    
        if not response:
            return ("Failed to get Linkedin Posts")
    
        return response
  • The @mcp.tool() decorator registers the get_linkedin_posts function as an MCP tool.
    async def get_linkedin_posts(init_date: str, end_date: str, blog_id: int) -> str | dict[str, Any]:
  • Input schema defined by function parameters and docstring: init_date (str, YYYY-MM-DD), end_date (str, YYYY-MM-DD), blog_id (int). Returns str or dict[str, Any].
    async def get_linkedin_posts(init_date: str, end_date: str, blog_id: int) -> str | dict[str, Any]:
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes a read operation ('Get') but doesn't mention permissions, rate limits, pagination, error handling, or what the returned list includes (e.g., post details, metadata). For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by a structured 'Args:' section. Each sentence earns its place by defining parameters, though it could be more concise by integrating the format details into the parameter descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 parameters, no annotations, no output schema), the description is partially complete. It covers the purpose and parameters adequately but lacks behavioral details (e.g., response format, error cases) and usage context. Without an output schema, it should ideally hint at what the returned list contains, which 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?

The description adds meaningful semantics for all three parameters: 'init date' and 'end date' define the period for data retrieval with format 'YYYY-MM-DD', and 'blog id' specifies the Metricool brand account. With 0% schema description coverage, this compensates well by explaining what each parameter represents, though it doesn't detail constraints like valid date ranges or blog ID sources.

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 clearly states the tool's purpose: 'Get the list of Linkedin Posts from your Metricool brand account.' It specifies the verb ('Get'), resource ('Linkedin Posts'), and scope ('from your Metricool brand account'). However, it doesn't explicitly differentiate from sibling tools like 'get_x_posts' or 'get_facebook_posts' beyond mentioning LinkedIn specifically.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_x_posts' for other platforms, nor does it specify prerequisites (e.g., authentication needs) or use cases beyond the basic date range and blog ID parameters. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/metricool/mcp-metricool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server