Skip to main content
Glama

get-user-profile

Retrieve LeetCode user profile data by providing a username to access contest history, problem statistics, and ranking information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesLeetCode username

Implementation Reference

  • The handler function that implements the core logic of the 'get-user-profile' tool: fetches the LeetCode user profile and returns it as formatted JSON or an error message.
    async ({ username }) => {
      try {
        const data = await leetcodeService.fetchUserProfile(username);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(data, null, 2)
          }]
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [{ type: "text", text: `Error: ${errorMessage}` }],
          isError: true
        };
      }
  • Input schema definition using Zod, specifying the required 'username' parameter.
    {
      username: z.string().describe("LeetCode username")
    },
  • Registration of the 'get-user-profile' tool on the MCP server, including schema and handler.
    server.tool(
      "get-user-profile",
      {
        username: z.string().describe("LeetCode username")
      },
      async ({ username }) => {
        try {
          const data = await leetcodeService.fetchUserProfile(username);
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify(data, null, 2)
            }]
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return {
            content: [{ type: "text", text: `Error: ${errorMessage}` }],
            isError: true
          };
        }
      }
    );
  • Supporting method in LeetCodeService that executes the GraphQL query to retrieve user profile data.
    /**
     * Fetch user profile data
     */
    async fetchUserProfile(username: string) {
      return this.executeQuery(userProfileQuery, { username });
    }
  • GraphQL query used to fetch comprehensive user profile information from LeetCode API.
    export const userProfileQuery = `
      query getUserProfile($username: String!) {
        matchedUser(username: $username) {
          username
          submitStats: submitStatsGlobal {
            acSubmissionNum {
              difficulty
              count
              submissions
            }
            totalSubmissionNum {
              difficulty
              count
              submissions
            }
          }
          profile {
            ranking
            reputation
            starRating
            realName
            aboutMe
            userAvatar
            skillTags
            country
            company
            school
            websites
            countryName
            location
            contestCount
            asciiCode
            socialAccounts
            skillSet {
              langLevels {
                langName
                langVerboseName
                level
              }
              topics {
                slug
                name
                level
              }
            }
          }
        }
      }
    `;
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/doggybee/mcp-server-leetcode'

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