Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_website_team

Read-only

Retrieve the team members assigned to a specific website by providing its ID.

Instructions

Get website team members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID

Implementation Reference

  • The tool 'get_website_team' is registered via server.tool() with the 'Get Website Team Members' description, a single input schema (website_id), and metadata options.
    server.tool(
      "get_website_team",
      "Get website team members.",
      {
        website_id: z.string().describe("The website ID"),
      },
      { title: "Get Website Team", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async ({ website_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/team`, "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The handler function for 'get_website_team' which takes website_id, calls the API endpoint /v1/workspace/website/{website_id}/team via GET, and returns the JSON response.
    async ({ website_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/team`, "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for 'get_website_team' requiring a single string parameter 'website_id' with a Zod schema description 'The website ID'.
    {
      website_id: z.string().describe("The website ID"),
    },
  • Metadata options for the tool including title 'Get Website Team', readOnlyHint: true, destructiveHint: false, openWorldHint: false.
    { title: "Get Website Team", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description aligns with that. No additional behavioral traits are disclosed beyond what annotations provide, but this is acceptable given the safety profile.

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 sentence with no fluff. It is front-loaded and efficient, though extremely brief.

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

Completeness3/5

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

Given the tool's simplicity (1 param, no output schema), the description is mostly adequate but lacks information about what is returned (e.g., list of team members). Could be more complete.

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% for the one parameter, and the description adds no extra meaning beyond 'The website ID.' With high coverage, baseline 3 is appropriate, but no value is added.

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 'Get website team members,' specifying the resource (website team) and action (get). However, it does not differentiate from the sibling tool 'get_workspace_team,' which could cause confusion about scope.

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 'get_workspace_team' or 'add_workspace_team_member.' There are no prerequisites or exclusions mentioned.

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

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