Skip to main content
Glama
123Ergo

unphurl-mcp

create_profile

Create or update a custom scoring profile to adjust URL risk assessment weights for specific use cases like cold email filtering, security monitoring, or SEO auditing.

Instructions

Create or update a custom scoring profile. Profiles are sparse overrides: only specify the weights you want to change. Everything else keeps its default value.

If a profile with this name already exists, it is updated with the new weights (full replacement, not merge).

Weights are points, not percentages. Each weight is the number of points that signal adds to the score when it fires. They don't need to total 100. A profile with weights totalling 90 is conservative (max possible score is 90). A profile with weights totalling 130 is aggressive (multiple signals quickly push to the cap of 100). The threshold the agent sets for action matters more than the weight totals.

Use show_defaults to see all 23 signals with their default weights and descriptions before creating a profile. Use check_url or check_urls with the "profile" parameter to score results with this profile.

Maximum 20 profiles per account. Profile name "default" is reserved.

Common profiles:

  • Cold email: weight parked (30), chain_incomplete (25), ssl_invalid (15) higher. Lower brand_impersonation (10).

  • Security bot: keep brand_impersonation high (40), increase domain_age_7 (30), redirects_5 (25).

  • Lead gen: weight parked (35), http_only (20), chain_incomplete (20) for dead business detection.

  • SEO audit: weight redirects_5 (30), chain_incomplete (30), parked (25) for link quality.

See the Unphurl API documentation for all 19 use case weight examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProfile name (lowercase alphanumeric and hyphens only, 1-50 chars, e.g. 'cold-email', 'security-bot')
weightsYesCustom weights for scoring signals. Only include signals you want to override. Available signals: brand_impersonation (default 40), domain_age_3 (35), domain_age_7 (25), domain_age_30 (15), domain_age_90 (5), ssl_invalid (10), http_only (5), redirects_3 (10), redirects_5 (25), chain_incomplete (15), parked (10), compound (10), phishing_floor (80), url_long (3), path_deep (3), subdomain_excessive (5), domain_entropy_high (5), url_contains_ip (10), encoded_hostname (5), tld_redirect_change (5), expiring_soon (10), domain_status_bad (15), no_mx_record (5).
Behavior4/5

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

With no annotations provided, the description carries full burden and does an excellent job explaining key behavioral traits: sparse overrides (only specify weights to change), full replacement on update (not merge), weight interpretation (points not percentages), profile limits (20 per account), and reserved names. It doesn't cover error conditions or response format, but provides substantial operational context.

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 appropriately sized and front-loaded with the core functionality. Every sentence adds value, though the API documentation reference at the end feels slightly extraneous. The structure moves logically from basic operation to weight interpretation to usage examples.

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?

For a mutation tool with no annotations and no output schema, the description provides substantial context about behavior, constraints, and usage patterns. It covers the sparse override model, update behavior, weight interpretation, limits, and practical examples. The main gap is lack of information about return values or error conditions, but overall it's quite comprehensive.

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 100% schema description coverage, the baseline is 3, but the description adds significant value beyond the schema. It explains that 'weights are points, not percentages' and provides practical examples of weight totals (90=conservative, 130=aggressive). The common profile examples give concrete context for how to structure weight objects, though it doesn't add syntax details beyond the schema's signal list.

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?

The description clearly states the tool's purpose as 'Create or update a custom scoring profile' with specific details about sparse overrides and full replacement behavior. It distinguishes this tool from siblings like 'delete_profile', 'list_profiles', and 'show_defaults' by explaining its unique create/update functionality.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: 'Use show_defaults to see all 23 signals... before creating a profile' and 'Use check_url or check_urls with the "profile" parameter to score results with this profile.' It also mentions the 'default' profile is reserved and maximum 20 profiles per account.

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/123Ergo/unphurl-mcp'

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