Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rover_sitter_profile

Retrieve a Rover sitter or walker profile by slug to view bio, ratings, reviews, services, pricing, experience, and location.

Instructions

Get Rover sitter profile. Returns a Rover sitter/walker profile: name, photo, bio, star rating, review count, repeat-client count, years of experience, neighborhood/city/state, starting price, Star Sitter status, the services offered with per-service pricing, and public review excerpts from the sitter's own profile page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesRover sitter profile slug, the trailing path segment of a search result's profile_url field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the returned data fields and that excerpts come from the sitter's own profile page. However, it does not explicitly state read-only/no side effects, access constraints, or error behavior, so it is adequate rather than thorough.

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?

Two efficiently structured sentences: the first states the action, the second front-loads the return contents. No filler or repetition.

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

Completeness4/5

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

The description is nearly complete for a simple profile-fetch tool with no output schema, because it enumerates the relevant returned fields. It could be fuller by clarifying how this tool relates to the sibling search tool, but the parameter schema covers how to call it correctly.

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?

There is one required parameter and schema description coverage is 100%, so the schema already explains that 'slug' is the trailing path segment of a search result's profile_url. The description adds no parameter-level meaning beyond that, which matches the baseline for fully covered schemas.

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?

States a specific verb and resource ('Get Rover sitter profile') and enumerates the returned profile fields, so the agent knows exactly what this tool retrieves. It does not explicitly distinguish itself from sibling tools such as rover_sitter_search or rover_trainer_profile, keeping it just below a 5.

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?

The description gives no guidance on when to use this profile tool versus the sibling search tool, nor any prerequisites or exclusions. Usage is only implied by the phrase 'Get ... profile'.

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

Deploy Server

Other Tools