Create signal
create_signalGenerate a concise meta description for the create_signal tool on the Bisibility MCP server, following the given constraints.
Instructions
Ingest a signal for the key-scoped project: an external event such as a deploy, CMS content change, or custom API event that may explain ranking movements. source must be deploy, cms, or api; type is a dot-separated identifier such as "deploy.completed" or "cms.page_updated". Optionally attach an ISO-8601 happened_at (defaults to now), a related keyword_id, an http(s) url, a severity (info, warning, or critical), and a JSON payload of up to 8KB.
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": {
"source": "<source>",
"type": "<type>"
},
"name": "create_signal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | url HTTP or HTTPS URL supplied by the endpoint owner. | |
| type | Yes | Dot-separated signal type such as "deploy.completed". | |
| source | Yes | System or workflow that produced the new signal. | |
| payload | No | JSON object payload. Serialized payloads above 8KB are rejected. | |
| severity | No | Signal severity. Defaults to "info". | |
| keyword_id | No | Identifier of the tracked keyword to operate on. | |
| project_id | No | Identifier of the bisibility project to operate on; list_projects returns valid project ids. | |
| happened_at | No | ISO-8601 date-time when the signal happened. Defaults to now on the server. | |
| idempotency_key | No |