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

admin_get_limits_usage

Retrieve current usage statistics against configured rate limits for a LinkedIn account. Input account UUID to monitor API consumption and prevent rate limit issues.

Instructions

Get current usage against configured rate limits for an account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesAccount UUID

Implementation Reference

  • The handler/execute function that calls admin.limits.getUsage(args) to retrieve current rate limit usage for a given account.
    public override async execute({
      admin,
      args,
    }: {
      admin: LinkedApiAdmin;
      args: TGetLimitsUsageParams;
    }): Promise<{ usage: Array<TLimitUsage> }> {
      return await admin.limits.getUsage(args);
    }
  • Zod schema defining the required input parameter: accountId (string).
    protected readonly schema = z.object({
      accountId: z.string(),
    });
  • MCP Tool schema definition with description and inputSchema declaring accountId as required string.
    public override getTool(): Tool {
      return {
        name: this.name,
        description: 'Get current usage against configured rate limits for an account.',
        inputSchema: {
          type: 'object',
          properties: {
            accountId: {
              type: 'string',
              description: 'Account UUID',
            },
          },
          required: ['accountId'],
        },
      };
    }
  • Tool registration: instantiated in the adminTools array of LinkedApiTools, making it available via adminToolByName().
    new AdminGetLimitsUsageTool(),
  • Abstract base class AdminTool that AdminGetLimitsUsageTool extends. Provides validate() and enforces execute() and getTool() contracts.
    export abstract class AdminTool<TParams, TResult> {
      public abstract readonly name: string;
      protected abstract readonly schema: z.ZodSchema;
    
      public abstract getTool(): Tool;
    
      public validate(args: unknown): TParams {
        return this.schema.parse(args) as TParams;
      }
    
      public abstract execute({
        admin,
        args,
      }: {
        admin: LinkedApiAdmin;
        args: TParams;
      }): Promise<TResult>;
    }
Behavior3/5

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

The description implies a read-only operation but lacks explicit statements about side effects or safety. Since no annotations exist, more detail would be beneficial, but the basic intent is clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that directly conveys the tool's purpose. No unnecessary words or redirection.

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

Completeness4/5

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

For a simple tool with one required parameter and no output schema, the description is adequate. It explains what the tool does clearly, though it could hint at the response format.

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 coverage is 100% with a clear description for accountId ('Account UUID'). The description adds no additional meaning beyond what the schema provides.

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 gets current usage against rate limits for an account. It uses a specific verb and resource, distinguishing it from sibling tools like admin_get_accounts or admin_set_limits.

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 on when to use this tool versus alternatives like admin_get_accounts or admin_get_subscription_status. No context on prerequisites or conditions.

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