Skip to main content
Glama

Get public Seenly profile

get_public_profile
Read-only

Fetch a public live Seenly video-resume profile by its URL slug (the part after /u/). Returns a public card (name, role, location, skills, profile URL). Unlisted drafts, missing slugs, and non-live profiles return not found. Never use this to reach a private draft.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_public_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPublic profile slug, such as jordan-mason from seenly.live/u/jordan-mason.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by naming the returned card fields and the failure modes (missing slug, unlisted draft, non-live profile all yield not found). It doesn't discuss rate limits or caching, so it falls short of the top score.

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?

Three short sentences, front-loaded with the verb, resource, and scope, then the return shape, then the exclusions. No filler or redundant restatement of the title.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description covers input format, return contents, error behavior, and the key misuse boundary. Nothing material is missing for an agent to call it correctly.

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?

With one parameter at 100% schema coverage the baseline is 3, and the description adds meaning by clarifying that the slug is the segment after /u/ in the public profile URL. That framing matters because other Seenly identifiers (e.g. signup links) could be confused with it.

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?

States a specific verb (Fetch) and resource (public live Seenly video-resume profile by URL slug) plus the shape of what comes back (name, role, location, skills, profile URL). It clearly scopes to public/live profiles, which separates it from the sibling utilities about_seenly and get_signup_link.

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

Usage Guidelines4/5

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

Gives explicit use context (identify a profile by its slug, the part after /u/) and an explicit exclusion: never use it to reach a private draft, and unlisted drafts or non-live profiles return not found. It doesn't name an alternative for private-draft access, but the when-to-use and when-not guidance is otherwise unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources