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

retrieve_ssi

Retrieve your current Social Selling Index score to measure LinkedIn sales effectiveness and track professional networking performance.

Instructions

Allows you to retrieve your current SSI (Social Selling Index) (st.retrieveSSI action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The RetrieveSSITool class implements the 'retrieve_ssi' tool. It maps to the 'retrieveSSI' operation, defines an empty Zod input schema for validation, sets the tool name and description, and returns the MCP Tool object definition.
    export class RetrieveSSITool extends OperationTool<unknown, unknown> {
      public override readonly operationName = OPERATION_NAME.retrieveSSI;
      public override readonly name = 'retrieve_ssi';
      protected override readonly schema = z.object({});
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to retrieve your current SSI (Social Selling Index) (st.retrieveSSI action).',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        };
      }
  • Registers the RetrieveSSITool (at line 53) as part of the LinkedApiTools class, instantiating it with a progress callback and adding to the readonly tools array.
    this.tools = [
      // Standard tools
      new SendMessageTool(progressCallback),
      new GetConversationTool(progressCallback),
      new CheckConnectionStatusTool(progressCallback),
      new RetrieveConnectionsTool(progressCallback),
      new SendConnectionRequestTool(progressCallback),
      new WithdrawConnectionRequestTool(progressCallback),
      new RetrievePendingRequestsTool(progressCallback),
      new RemoveConnectionTool(progressCallback),
      new SearchCompaniesTool(progressCallback),
      new SearchPeopleTool(progressCallback),
      new FetchCompanyTool(progressCallback),
      new FetchPersonTool(progressCallback),
      new FetchPostTool(progressCallback),
      new ReactToPostTool(progressCallback),
      new CommentOnPostTool(progressCallback),
      new CreatePostTool(progressCallback),
      new RetrieveSSITool(progressCallback),
      new RetrievePerformanceTool(progressCallback),
      // Sales Navigator tools
      new NvSendMessageTool(progressCallback),
      new NvGetConversationTool(progressCallback),
      new NvSearchCompaniesTool(progressCallback),
      new NvSearchPeopleTool(progressCallback),
      new NvFetchCompanyTool(progressCallback),
      new NvFetchPersonTool(progressCallback),
      // Other tools
      new ExecuteCustomWorkflowTool(progressCallback),
      new GetWorkflowResultTool(progressCallback),
      new GetApiUsageTool(progressCallback),
    ];
  • The execute method in OperationTool (base class for RetrieveSSITool) that handles the tool execution: finds the LinkedAPI operation by operationName ('retrieveSSI'), validates args, and calls executeWithProgress to run it.
      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,
        });
      }
    }
  • Zod schema for input validation of retrieve_ssi tool (empty object, no parameters expected).
    protected override readonly schema = z.object({});
  • Overrides getTool() to provide the MCP-compatible Tool object with name 'retrieve_ssi', description, and empty inputSchema.
    public override getTool(): Tool {
      return {
        name: this.name,
        description:
          'Allows you to retrieve your current SSI (Social Selling Index) (st.retrieveSSI action).',
        inputSchema: {
          type: 'object',
          properties: {},
        },
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks critical details: whether this requires specific permissions, if it's rate-limited, what format the SSI data returns (score breakdown, trends), or if it's user-specific versus workspace-wide. The mention of 'st.retrieveSSI action' is implementation detail that doesn't help the agent.

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 brief but includes unnecessary implementation detail ('st.retrieveSSI action') that doesn't aid the agent. The first part is clear, but the parenthetical reference could be omitted for better focus. It's not excessively verbose, but not optimally streamlined.

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 no annotations, no output schema, and a simple zero-parameter design, the description is incomplete. It fails to explain what the SSI score represents, how it's calculated, or what the return format includes (e.g., numerical score, components, timestamp). For a metric-retrieval tool, this leaves the agent guessing about the output's structure and utility.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description appropriately doesn't add parameter information, maintaining focus on the tool's purpose without redundancy. A baseline of 4 is applied for zero-parameter tools.

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 resource ('your current SSI (Social Selling Index)'), making the purpose understandable. It distinguishes from siblings by focusing on SSI retrieval rather than connections, posts, or searches. However, it doesn't explicitly differentiate from 'retrieve_performance' which might be a related metric.

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 prerequisites (e.g., authentication status), timing considerations, or how it differs from sibling tools like 'retrieve_performance' or 'get_api_usage' that might provide related metrics.

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