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

check_connection_status

Verify LinkedIn connection status with any profile using their public URL to determine if you're connected, pending, or not connected.

Instructions

Allows you to check the connection status between your account and another person (st.checkConnectionStatus action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
personUrlYesPublic or hashed LinkedIn URL of the person you want to check the connection status with. (e.g., 'https://www.linkedin.com/in/john-doe')

Implementation Reference

  • The CheckConnectionStatusTool class defines the core handler for the 'check_connection_status' tool, specifying its name, the underlying Linked API operation name, Zod schema for input validation, and the MCP-compatible tool definition including detailed input schema.
    export class CheckConnectionStatusTool extends OperationTool<
      TCheckConnectionStatusParams,
      TCheckConnectionStatusResult
    > {
      public override readonly name = 'check_connection_status';
      public override readonly operationName = OPERATION_NAME.checkConnectionStatus;
      protected override readonly schema = z.object({
        personUrl: z.string(),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to check the connection status between your account and another person (st.checkConnectionStatus action).',
          inputSchema: {
            type: 'object',
            properties: {
              personUrl: {
                type: 'string',
                description:
                  "Public or hashed LinkedIn URL of the person you want to check the connection status with. (e.g., 'https://www.linkedin.com/in/john-doe')",
              },
            },
            required: ['personUrl'],
          },
        };
      }
    }
  • Zod schema used for runtime input validation of the tool parameters.
    protected override readonly schema = z.object({
      personUrl: z.string(),
    });
  • Imports the CheckConnectionStatusTool for use in LinkedApiTools.
    import { CheckConnectionStatusTool } from './tools/check-connection-status.js';
  • Instantiates the CheckConnectionStatusTool and registers it in the tools array of the LinkedApiTools class.
    new CheckConnectionStatusTool(progressCallback),
  • Base class for operation-based tools providing the execute method that dynamically resolves and invokes the corresponding Linked API operation based on operationName, handling progress reporting.
    export abstract class OperationTool<TParams, TResult> extends LinkedApiTool<TParams, TResult> {
      public abstract readonly operationName: TOperationName;
    
      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,
        });
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action name ('st.checkConnectionStatus') but doesn't explain what the tool actually returns (e.g., whether it shows connection strength, mutual connections, or just binary status). It also doesn't mention authentication requirements, rate limits, or potential side effects.

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 gets straight to the point. While it could be more informative, it doesn't waste words or include unnecessary information. The action name reference ('st.checkConnectionStatus') is somewhat technical but doesn't significantly detract from conciseness.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned about connection status, what possible status values are, or how to interpret results. Given the complexity of social connection status (which could involve degrees of connection, pending requests, etc.), more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents the single 'personUrl' parameter. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'check[s] the connection status between your account and another person', which is a clear verb+resource combination. However, it doesn't distinguish this from sibling tools like 'retrieve_connections' or 'retrieve_pending_requests', leaving ambiguity about what specific aspect of connection status is being checked.

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 when this tool is appropriate versus 'retrieve_connections' (which might list all connections) or 'retrieve_pending_requests' (which might show pending invitations). There's no context about prerequisites or limitations.

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