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

retrieve_pending_requests

Retrieve pending LinkedIn connection requests sent from your account to manage outreach and follow up on networking opportunities.

Instructions

Allows you to retrieve pending connection requests sent from your account. (st.retrievePendingRequests action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the RetrievePendingRequestsTool class, which implements the tool handler by extending OperationTool, setting the name 'retrieve_pending_requests', mapping to the specific LinkedAPI operation, defining empty input schema, and providing the MCP tool definition.
    export class RetrievePendingRequestsTool extends OperationTool<unknown, unknown> {
      public override readonly name = 'retrieve_pending_requests';
      public override readonly operationName = OPERATION_NAME.retrievePendingRequests;
      protected override readonly schema = z.object({});
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to retrieve pending connection requests sent from your account. (st.retrievePendingRequests action).',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        };
      }
    }
  • Registers the RetrievePendingRequestsTool instance in the LinkedApiTools constructor's tools array.
    new RetrievePendingRequestsTool(progressCallback),
  • The core execute method in OperationTool that handles the tool execution by locating the matching LinkedAPI operation based on operationName and invoking 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,
      });
    }
  • Defines the input schema as an empty object using Zod, indicating no parameters are required.
    protected override readonly schema = z.object({});
  • Imports the RetrievePendingRequestsTool class for use in registration.
    import { RetrievePendingRequestsTool } from './tools/retrieve-pending-requests.js';
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. It states it retrieves pending requests but doesn't disclose behavioral traits such as authentication needs, rate limits, pagination, or what 'pending' entails. This leaves significant gaps for a tool that likely involves network operations.

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 front-loads the core purpose. It includes an internal reference ('st.retrievePendingRequests action') which adds minor noise but doesn't significantly detract from clarity.

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 the tool's likely complexity in handling connection requests, the description is incomplete. It lacks details on return format, error conditions, or operational constraints, making it inadequate for safe and effective use by an agent.

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 schema description coverage is 100%, so no parameter information is needed. The description doesn't add param details, but this is acceptable given the lack of parameters, aligning with the baseline for zero params.

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 'pending connection requests sent from your account', which is specific and unambiguous. It distinguishes itself from siblings like 'retrieve_connections' by specifying 'pending' and 'sent from your account', though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like 'retrieve_connections' or 'check_connection_status'. The description implies usage for pending sent requests but doesn't specify exclusions or contextual triggers.

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