get_profileGet a person's verified professional profile - headline, summary, employment history with highlights, skills and education - from their Tazilo profile URL or handle. Returns markdown.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | The person's Tazilo profile URL or handle: 'https://tazilo.ai/@sathishgs', 'tazilo.ai/@sathishgs', '@sathishgs' or 'sathishgs'. | |
| sections | No | Only these sections. Omit for the whole profile. |
Changes observed during successful MCP inspections.
Input schema / properties / sections / items / enumPrevious value: -[
- "summary",
- "experience",
- "skills",
- "education"
-]New value: +[
+ "summary",
+ "experience",
+ "skills",
+ "education",
+ "context"
+]Input schema / properties / sections / maxItemsPrevious value: -4New value: +5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the return format ('Returns markdown'), which is genuinely useful since there is no output schema, but says nothing about behavior when the profile is missing, private, or when a single section is unavailable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences: what is retrieved first, then the input source, then the return format. No boilerplate and nothing that could be cut without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter read tool with annotations covering safety, the description plus schema give an agent everything needed to invoke it, and it correctly notes the markdown return format in the absence of an output schema. Only error/edge-case behavior for unknown or restricted handles is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the 'handle' description already spells out the four accepted URL/handle forms with examples, so the description's mention of 'URL or handle' is redundant. The 'sections' parameter is not mentioned at all in the description, though the schema documents it adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get a person's verified professional profile') and enumerates the content returned (headline, summary, employment history, skills, education), which is far more than the title provides. It does not differentiate from the sibling 'ask', but the sibling name alone is uninformative, so differentiation is not really achievable here.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the input ('from their Tazilo profile URL or handle') but there is no explicit when-to-use guidance, no mention of when a user should call 'ask' instead, and no statement about failure modes such as a nonexistent handle.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.