Skip to main content
Glama
pubrio

Pubrio

Official

create_monitor

Set up a signal monitor to track jobs, news, or advertisements for specified companies and receive alerts via email, webhook, or outreach sequence.

Instructions

Create a new signal monitor to track jobs, news, or advertisements for specified companies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMonitor name
emailNoEmail address (required when destination_type is "email")
domainsNoComma-separated company domains to monitor
companiesNoComma-separated company UUIDs to monitor
descriptionNoMonitor description
webhook_urlNoWebhook URL (required when destination_type is "webhook")
signal_typesYesSignal types to monitor: "jobs", "news", "advertisements"
linkedin_urlsNoComma-separated company LinkedIn URLs to monitor
detection_modeYesDetection mode: "new" or "new_and_updated"
signal_filtersNoSignal-specific filters array
company_filtersNoAdvanced company filters as JSON string
destination_typeYesDestination type: "webhook", "email", or "outreach_sequence"
frequency_minuteNoCheck frequency in minutes
max_daily_triggerNoMaximum daily triggers
notification_emailNoEmail for failure notifications
retry_delay_secondNoRetry delay in seconds
max_failure_triggerNoMaximum failure triggers before pausing
sequence_identifierNoOutreach sequence identifier (required when destination_type is "outreach_sequence")
is_people_enrichmentNoEnable people enrichment on trigger
is_company_enrichmentNoEnable company enrichment on trigger
max_retry_per_triggerNoMaximum retries per trigger
max_records_per_triggerNoMaximum records per trigger
people_enrichment_configsNoPeople enrichment configuration array
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states creation without mentioning side effects, authentication needs, rate limits, or success response. This is insufficient for a mutation tool with 23 parameters.

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 concise sentence with no redundancy. However, it could be slightly more structured with additional information about prerequisites or outcomes without harming conciseness.

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

Completeness2/5

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

Given the tool's complexity (23 parameters, no output schema, no annotations), the description is too brief. It lacks return value details, error handling, and the overall monitor lifecycle context, making it incomplete for an AI agent.

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%, so the schema already documents parameters. The description adds no extra meaning beyond the schema's field descriptions, achieving the baseline score.

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 the action 'Create' and the resource 'new signal monitor', and specifies the tracked signal types (jobs, news, advertisements) and target (specified companies). This differentiates it from update and delete tools.

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 on when to use this tool versus alternatives like lookup endpoints or existing monitors. Prerequisites (e.g., company UUIDs) are not mentioned, and there are no exclusion criteria.

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

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