Skip to main content
Glama

profiles

Retrieve and enrich professional profiles using a LinkedIn URL or a person's name and company.

Instructions

Find and enrich a professional profile by LinkedIn URL or name + company. Cost: 3 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkedin_urlNoLinkedIn profile URL (fastest path)
first_nameNoPerson's first name
last_nameNoPerson's last name
companyNoCompany name to narrow search

Implementation Reference

  • Schema definition for the 'profiles' tool: defines the capability name, description, and input schema (linkedin_url, first_name, last_name, company).
    {
      name: "profiles",
      description: "Find and enrich a professional profile by LinkedIn URL or name + company. Cost: 3 credits.",
      inputSchema: {
        linkedin_url: z.string().optional().describe("LinkedIn profile URL (fastest path)"),
        first_name: z.string().optional().describe("Person's first name"),
        last_name: z.string().optional().describe("Person's last name"),
        company: z.string().optional().describe("Company name to narrow search"),
      },
  • src/index.ts:246-258 (registration)
    Registration loop that registers all capabilities (including 'profiles') as MCP tools on the server using server.registerTool(). The handler delegates to callSuprsonic(cap.name, args).
    // Register each capability as an MCP tool
    for (const cap of CAPABILITIES) {
      // Cast inputSchema to avoid TS2589 (excessively deep type instantiation from Zod chains)
      server.registerTool(
        cap.name,
        {
          description: cap.description,
          inputSchema: cap.inputSchema as any,
        },
        async (args: any): Promise<CallToolResult> => {
          return callSuprsonic(cap.name, args as Record<string, unknown>);
        },
      );
  • The generic HTTP handler (callSuprsonic) that executes all tool logic including 'profiles'. It sends the capability name and params to the Suprsonic REST API at POST /v1/agent.
    async function callSuprsonic(capability: string, params: Record<string, unknown>): Promise<CallToolResult> {
      if (!API_KEY) {
        return {
          content: [{ type: "text", text: "Error: SUPRSONIC_API_KEY environment variable is not set. Get your key at https://suprsonic.ai/app/apis" }],
          isError: true,
        };
      }
    
      try {
        const resp = await fetch(`${BASE_URL}/v1/agent`, {
          method: "POST",
          headers: {
            "Authorization": `Bearer ${API_KEY}`,
            "Content-Type": "application/json",
          },
          body: JSON.stringify({ capability, params }),
        });
    
        const result = await resp.json() as any;
    
        // Handle non-envelope responses (401, 429, etc. return {"detail": ...})
        if (result.detail && result.success === undefined) {
          const msg = typeof result.detail === "object" ? (result.detail.title || result.detail.detail || JSON.stringify(result.detail)) : String(result.detail);
          return {
            content: [{ type: "text", text: `Error (HTTP ${resp.status}): ${msg}` }],
            isError: true,
          };
        }
    
        if (!result.success) {
          const errMsg = result.error?.detail || result.error?.title || "Request failed";
          return {
            content: [{ type: "text", text: `Error: ${errMsg}` }],
            isError: true,
          };
        }
    
        const text = JSON.stringify(result.data, null, 2);
        const meta = result.metadata
          ? `\n\n[Provider: ${(result.metadata as any).provider_used || "unknown"}, ${(result.metadata as any).response_time_ms || 0}ms, ${result.credits_used || 0} credits]`
          : "";
    
        return {
          content: [{ type: "text", text: text + meta }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Network error: ${err instanceof Error ? err.message : String(err)}` }],
          isError: true,
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description only states 'enrich' and a cost of 3 credits, but fails to disclose what enrichment entails, rate limits, authentication needs, or any side effects. This is insufficient for a tool without annotation support.

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 extremely concise (two short sentences) and front-loads both the purpose and usage methods without any filler.

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?

Without an output schema, the description does not explain the return format or what data is included in the enrichment. Given the tool's complexity (finding and enriching profiles), this omission leaves the agent uncertain about the response structure.

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?

Schema coverage is 100%, but the description adds meaningful context: 'fastest path' for linkedin_url and 'narrow search' for company, enhancing parameter understanding beyond the schema definitions.

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

Purpose5/5

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

The description clearly states the tool finds and enriches a professional profile using LinkedIn URL or name+company, with a specific verb and resource, distinguishing it from broader tools like 'search' or 'scrape'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions two usage paths (LinkedIn URL or name+company) but lacks guidance on when to prefer one over the other or when not to use this tool compared to siblings like 'search' or 'companies'.

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/O-mega-Enterprise/suprsonic-mcp'

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