Skip to main content
Glama
Linked-API
by Linked-API

retrieve_performance

Retrieve performance analytics from your LinkedIn dashboard to track campaign metrics and engagement data.

Instructions

Allows you to retrieve performance analytics from your LinkedIn dashboard (st.retrievePerformance action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The RetrievePerformanceTool class is the primary handler for the 'retrieve_performance' tool. It specifies the tool name, maps to the LinkedIn API operation 'retrievePerformance', defines an empty input schema, and provides the MCP Tool definition.
    export class RetrievePerformanceTool extends OperationTool<unknown, unknown> {
      public override readonly name = 'retrieve_performance';
      public override readonly operationName = OPERATION_NAME.retrievePerformance;
      protected override readonly schema = z.object({});
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to retrieve performance analytics from your LinkedIn dashboard (st.retrievePerformance action).',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        };
      }
    }
  • Core execution handler in OperationTool base class, which locates the specific LinkedIn API operation by name (retrievePerformance for this tool) and executes it with progress tracking.
    public override execute({
      linkedapi,
      args,
      workflowTimeout,
      progressToken,
    }: {
      linkedapi: LinkedApi;
      args: TParams;
      workflowTimeout: number;
      progressToken?: string | number;
    }): Promise<TMappedResponse<TResult>> {
      const operation = linkedapi.operations.find(
        (operation) => operation.operationName === this.operationName,
      )! as Operation<TParams, TResult>;
      return executeWithProgress(this.progressCallback, operation, workflowTimeout, {
        params: args,
        progressToken,
      });
    }
  • Registers the retrieve_performance tool by instantiating RetrievePerformanceTool and including it in the LinkedApiTools collection, which is then exposed via the MCP server.
    new RetrievePerformanceTool(progressCallback),
  • Import statement for the RetrievePerformanceTool class.
    import { RetrievePerformanceTool } from './tools/retrieve-performance.js';
  • Zod schema definition for tool inputs (empty object, no parameters required).
    protected override readonly schema = z.object({});
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 only states what the tool does ('retrieve performance analytics') without detailing traits like whether it's read-only, has side effects, requires specific permissions, or handles errors. This is insufficient for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the key action. A minor improvement could be adding a brief note on output or usage context to enhance completeness.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'performance analytics' includes, the format of the return data, or any behavioral aspects like rate limits or authentication needs. For a retrieval tool with no structured support, more detail is needed.

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 has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it meets the baseline for no parameters. However, it doesn't explicitly state 'no parameters required', which could slightly improve clarity.

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 verb 'retrieve' and the resource 'performance analytics from your LinkedIn dashboard', which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'get_api_usage' or 'retrieve_connections', which could also involve LinkedIn data retrieval, so it doesn't reach the highest score.

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 context, prerequisites, or exclusions, such as whether it requires authentication or if there are rate limits. This leaves the agent with little direction.

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

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/Linked-API/linkedapi-mcp'

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